{"version":"2.1.299","anchor":"mcp-always-allow-shadowing-and-managed-policy-handling","canonical_anchor":"mcp-always-allow-shadowing-and-managed-policy-handling","heading":"Some MCP servers that would be disabled can now stay enabled","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-always-allow-shadowing-and-managed-policy-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Some MCP servers that would be disabled can now stay enabled\n\nMCP servers that would have been disabled now stay enabled when a new check on the server passes\n\n**Unclear.** It is not stated what the new check on a server tests, so it is unclear which servers now stay enabled.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Claude Code now skips disabling some MCP servers it would otherwise have disabled, when a new check on that server passes. The information Claude Code uses to decide tool permissions also now records which setting overrides an \"always allow\" rule for an MCP tool.\n\n**Why**\n\nThis affects which MCP servers stay switched on and which of their tools are allowed without asking.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}