{"version":"2.1.293","anchor":"plugin-mcp-tool-policy-matching-extended","canonical_anchor":"plugin-mcp-tool-policy-matching-extended","heading":"Admin tool policies now match plugin MCP tool names regardless of case","tier":"notice","area":"Permissions","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/plugin-mcp-tool-policy-matching-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Admin tool policies now match plugin MCP tool names regardless of case\n\nManaged tool policy patterns for MCP tools from plugins now match regardless of case, and two policy sets can be merged keeping the strictest\n\n**Unclear.** Whether these policy changes apply to the Claude Code command-line tool or only to the desktop app.\n\n**What**\n\nAdministrators can set managed tool policies, rules saying which tools are allowed. MCP tools are tools from outside services connected through the Model Context Protocol, and those that come from plugins have names starting `mcp__plugin_`, then the plugin name, then an underscore. Policy patterns for these names now match whatever the upper or lower case. Before, matching was case-sensitive.\n\nTwo sets of policies can now also be merged, keeping the strictest rule for each tool, and policies for plugin MCP tools can be looked up by name.\n\n**Why**\n\nThis affects how administrator policies apply to MCP tools that come from plugins. A rule written with different capitals from the tool's name now still applies.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: yes"}