{"version":"2.1.321","anchor":"mcp-connections-refused-when-headers-fall-under-an-organizat","canonical_anchor":"mcp-connections-refused-when-headers-fall-under-an-organizat","heading":"Organizations can block MCP server connections that send certain headers","tier":"notice","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-connections-refused-when-headers-fall-under-an-organizat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Organizations can block MCP server connections that send certain headers\n\nClaude Code skips connecting to an MCP server when the headers it would send fall under an organization's connector block\n\n**Unclear.** Where the organization's connector block is set, and which users it applies to, is not stated.\n\n**What**\n\nMCP servers are add-on programs that give Claude extra tools. Some are reached over the network. Before connecting to one of these, Claude Code now checks the headers it is about to send against a block set by your organization's managed policy. Headers are extra pieces of information sent with each request.\n\nIf the headers match the block, Claude Code does not connect. The server shows as failed with a managed-policy reason, and the log says the connection was skipped because the headers are under the organization's connector block.\n\n**Why**\n\nOrganizations can now stop specific MCP servers from connecting based on their headers. If a server you use suddenly fails with a managed-policy reason, this block is the cause.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}