{"version":"2.1.318","anchor":"mcp-deniedmcpservers-matches-mcp-url-parameter-addresses","canonical_anchor":"mcp-deniedmcpservers-matches-mcp-url-parameter-addresses","heading":"MCP server deny lists now catch addresses hidden in an mcp_url parameter","tier":"notice","area":"MCP","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-deniedmcpservers-matches-mcp-url-parameter-addresses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### MCP server deny lists now catch addresses hidden in an mcp_url parameter\n\nA `deniedMcpServers` URL entry now also blocks a server whose address carries that URL in its mcp_url part, and command allow rules are stricter\n\n**What**\n\nTwo changes affect how the managed `deniedMcpServers` and `allowedMcpServers` settings are matched against MCP servers. MCP servers are outside tools Claude Code connects to.\n\n- `deniedMcpServers`: a `serverUrl` entry now also blocks a server when it matches the address inside that server's `mcp_url` parameter. Before, only the address the server actually connects to was checked. Claude Code shows a warning saying the server is blocked because of this match.\n\n- `allowedMcpServers`: when a server could be described by more than one command, every one of those commands now has to match an allowed entry, not just one.\n\n**Why**\n\nThis closes a way around an organization's deny list, where the blocked address could be wrapped inside another URL. Some servers that worked before may now be blocked.\n\n- Area: MCP\n- Names: `deniedMcpServers`, `allowedMcpServers`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}