{"version":"2.1.302","anchor":"mcp-gateway-removes-unowned-headers-on-unauthenticated-retry","canonical_anchor":"mcp-gateway-removes-unowned-headers-on-unauthenticated-retry","heading":"MCP connections retry once and check managed policy before and after connecting","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/mcp-gateway-removes-unowned-headers-on-unauthenticated-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### MCP connections retry once and check managed policy before and after connecting\n\nMCP connections now retry once, keeping track of headers Claude Code added, and check your organization's policy both before and after connecting\n\n**What**\n\nMCP servers are outside services that give Claude Code extra tools. Requests to them now work differently:\n\n- Claude Code tracks which request headers it added itself. After a check, it can try a request once more instead of giving up after one attempt.\n\n- An extra check against managed policy, your organization's settings, now runs both before and after connecting. A blocked server shows a message that the MCP server is blocked by managed policy.\n\n**Why**\n\nYour organization's MCP rules are enforced more strictly, so a server it blocks is caught even after the connection is made.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}