{"version":"2.1.310","anchor":"permission-denyask-rules-for-mcp-tools-also-check-other-den","canonical_anchor":"permission-denyask-rules-for-mcp-tools-also-check-other-den","heading":"Deny and ask rules for MCP tools can now match more tools","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/permission-denyask-rules-for-mcp-tools-also-check-other-den","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Deny and ask rules for MCP tools can now match more tools\n\nA deny or ask permission rule matched against an MCP tool now also checks your other deny and ask rules and a related parent rule, so it can cover more tools\n\n**Unclear.** Exactly which additional MCP tools a given deny or ask rule now covers is not spelled out.\n\n**What**\n\nMCP (Model Context Protocol) is a way to connect Claude Code to tools from other programs and services. Permission rules decide whether Claude Code may use a tool on its own (allow), must stop (deny), or must ask you first (ask).\n\nWhen a deny or ask rule is checked against an MCP tool, Claude Code now also tests it against your other deny and ask rules and against a parent rule derived from them. Before, a rule matched only by the tool's exact name, its family, an alias, or a wildcard pattern.\n\n**Why**\n\nA single deny or ask rule can now cover more MCP tools than before, so tools you meant to block or be asked about are more likely to be caught. If you rely on such rules, check that they do not now stop tools you wanted to allow.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}