{"version":"2.1.301","anchor":"mcp-server-filtering-now-explains-servers-kept-despite-allow","canonical_anchor":"mcp-server-filtering-now-explains-servers-kept-despite-allow","heading":"MCP server filtering now explains which servers it kept and how to remove them","tier":"notice","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/mcp-server-filtering-now-explains-servers-kept-despite-allow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### MCP server filtering now explains which servers it kept and how to remove them\n\nWhen MCP servers are filtered by policy, Claude Code now notes the ones it kept and says `deniedMcpServers` in managed settings removes them\n\n**What**\n\nMCP servers are add-on programs that give Claude Code extra tools. In safe, hermetic and enterprise modes, Claude Code filters the MCP servers it is given against an allowlist or policy. Before, this filtering reported only the servers it kept, the ones it dropped and a reason.\n\nIt now also produces notes about servers it kept anyway. The notes say two things:\n\n- MCP servers that Claude Code adds to its own remote sessions are not removed by the allowlist.\n\n- Listing them in `deniedMcpServers` in managed settings removes them.\n\n**Why**\n\nAdministrators can now see why a server survived an allowlist and how to block it if they want to.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}