{"version":"2.1.310","anchor":"mcp-tools-now-report-when-allow-rules-are-ignored-because-of","canonical_anchor":"mcp-tools-now-report-when-allow-rules-are-ignored-because-of","heading":"Claude Code now explains when MCP allow rules are ignored because of a duplicate name","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/mcp-tools-now-report-when-allow-rules-are-ignored-because-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Claude Code now explains when MCP allow rules are ignored because of a duplicate name\n\nIf another MCP server already uses a server's name, its allow rules are ignored and a warning now tells you how to fix it\n\n**What**\n\nAllow rules let you approve an MCP server's tools ahead of time, so you are not asked each time. MCP servers are outside tools Claude Code connects to. Claude Code now ignores a server's allow rules in these cases, and shows a warning when it does:\n\n- another MCP server already uses the same name\n\n- the name could not be recorded in the config file\n\nThe warning tells you to give the server a different name and write the rules for that new name, or to reconnect if the config file was busy. The existing warning about names that clash with claude.ai connectors is unchanged.\n\n**Why**\n\nWithout this warning, allow rules could stop applying with no explanation. Now you can see why you are being asked again and what to change.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}