{"version":"2.1.314","anchor":"mcp-tool-permission-rules-also-match-the-servers-denykey-al","canonical_anchor":"mcp-tool-permission-rules-also-match-the-servers-denykey-al","heading":"Permission rules for MCP tools also match another name the tool can go by","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-tool-permission-rules-also-match-the-servers-denykey-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Permission rules for MCP tools also match another name the tool can go by\n\nAllow and deny rules for MCP tools are now checked against an extra alternative name for each tool, so some deny rules may now apply where they did not\n\n**Unclear.** It is not stated when a server has a deny alias, so it is unclear how often this changes which rules match.\n\n**What**\n\nMCP tools are tools provided by outside servers you connect to Claude Code. Your permission rules, the allow and deny lists that decide which tools Claude may use, are checked against a tool's own name and against alternative names for it. Claude Code now builds one more alternative name from the server's deny alias, removes duplicates, and checks your rules against that too. Before, only one alternative name was used.\n\n**Why**\n\nA deny rule written using the alias name may now block an MCP tool it previously missed. If you rely on such rules, check that they now cover the tools you meant.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}