-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
-
Web proxy support for outbound calls to IDP or third party endpoints
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Server access control for MCP Gateway
MCP clients can connect to any backend MCP server, which can introduce critical security risks, such as data exfiltration, unauthorized tool usage, and enterprise policy bypasses.
To mitigate these risks, NetScaler® enforces server-level access control using allow list and block list policies at the gateway to deliver the following:
- Ensures that only approved MCP servers are accessible.
- Prevents unauthorized or malicious MCP endpoints.
- Provides centralized governance for MCP access.
- Provides a clear rejection response for disallowed requests.
This feature enables administrators to control the MCP servers that clients can access using NetScaler MCP Gateway. It uses content switching and responder policies to enforce allow or deny behavior based on request attributes, such as headers.
Important considerations
The feature relies on client-provided headers, for example x-netscaler-target-mcp-server. We recommend that you:
- Configure a deny policy as default.
- Combine with authentication and rate limiting for full security.
Prerequisites
Ensure that the following requirements are met:
- An MCP Gateway is configured on NetScaler using content switching and load balancing virtual servers.
- Backend MCP servers are configured.
- The client sends the target MCP header.
Configure allow list and block list using the CLI
Configure allow lists using content switching policies and enforce block lists using responder policies.
Sample allow list configuration
add cs policy allow_app1 "HTTP.REQ.HEADER(\"x-netscaler-target-mcp-server\").CONTAINS(\"app1.com\")"
bind cs vserver mcp_cs -policyName allow_app1 -priority 10 -gotoPriorityExpression NEXT
<!--NeedCopy-->
Sample block list configuration
add responder action deny_res_act respondwith q<"HTTP/1.1 403 Forbidden\r\nContent-Type: application/json\r\nContent-Length: 42\r\nConnection: close\r\n\r\n{\"error\":\"Unauthorized MCP server access\"}">
add responder policy deny_res_pol "HTTP.REQ.HEADER(\"x-netscaler-target-mcp-server\").CONTAINS(\"untrusted.com\")" deny_res_act
bind cs vserver mcp_cs -policyName deny_res_pol -priority 100 -gotoPriorityExpression END -type REQUEST
<!--NeedCopy-->
Sample default deny policy
add responder policy default_deny "TRUE" deny_res_act
bind cs vserver mcp_cs -policyName default_deny -priority 1000 -gotoPriorityExpression END -type REQUEST
<!--NeedCopy-->
Troubleshooting
Request blocked unexpectedly
Verify whether the header value matches the policy.
Unauthorized access is allowed
Check the policy priority order.
Client errors
Confirm the JSON response formatting.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.