Restrict remote MCP servers and tools with Global Secure Access MCP firewall
Implementation Effort: Medium - Requires an approved server/tool inventory, protocol-aware policy decisions, and application-owner coordination.
User Impact: Medium - Blocked servers or MCP primitives can prevent agent tasks from completing.
Overview
The Global Secure Access (GSA) Model Context Protocol (MCP) firewall can allow or block supported remote servers and primitives such as tools, resources, and prompt templates. It adds protocol-aware controls beyond allowing a destination domain.
This supports Use least privilege access by limiting exposed capabilities and Assume breach by constraining what a compromised client can invoke. It complements API Management gateway requirements and application authorization rather than replacing them.
Prerequisites
- Complete AI network readiness and obtain approval for preview use.
- Internet Access licensing, Global Secure Access Administrator access, and Conditional Access Administrator access.
- A supported GSA client on an Entra joined or hybrid-joined device or virtual machine, Internet Access forwarding, and Transport Layer Security (TLS) inspection.
- An approved server/tool inventory informed by remote MCP discovery, plus a safe test environment and accountable application owners.
Limitations
- The feature is in preview. An allowed server can still expose prohibited tools; destination approval alone does not establish tool-level permission.
- Inspection covers remote MCP using JSON-RPC 2.0 over streamable HTTP and Server-Sent Events. Local/stdio servers and JSON-RPC batches are not inspected.
- During preview, configured primitives may not display when a rule is reopened. The configuration guide documents how to inspect them through Microsoft Graph.
- Copilot Studio MCP logging support does not establish equivalent firewall-enforcement support.
- Network enforcement does not replace MCP OAuth/token validation or application-side authorization.