TL;DR
Cloudflare One now detects Model Context Protocol traffic, identifies shadow MCP servers, and enforces approved-path access through new Gateway policies and dashboards.
Key Points
- MCP-Protocol-Version header detection identifies MCP traffic on TLS-inspected requests without maintaining domain allowlists
- New MCP traffic dashboard shows which servers are accessed, which users access them, and whether requests bypass Portals
- Gateway Traffic Source selectors distinguish Portal-proxied MCP requests from direct device connections for policy enforcement
- Server-side controls (WriteGuard pattern) can block unauthorized tool calls before execution; network layer catches shadow MCP on managed paths
Why It Matters
AI agents can execute thousands of tool calls at inhuman speed with nondeterministic decisions, creating security risks traditional permission models weren't designed for. These controls let security teams detect unauthorized MCP servers (shadow MCP), prevent Portal bypasses, and block dangerous tool invocations before they execute—critical for organizations deploying Claude, Cursor, and other AI clients with MCP server access.
Source: blog.cloudflare.com