{"version":"2.1.314","anchor":"mcp-permission-dialog-warns-when-a-server-takes-over-another","canonical_anchor":"mcp-permission-dialog-warns-when-a-server-takes-over-another","heading":"MCP permission prompt warns when a server takes over another server's name","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-permission-dialog-warns-when-a-server-takes-over-another","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### MCP permission prompt warns when a server takes over another server's name\n\nMCP permission prompts now warn when another server owns this server's name, and that 'Don't ask again' moves the name and its allow rules\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. When one of their tools needs your permission, Claude Code shows a permission prompt.\n\n- Permission requests now carry a `takesOverServerName` value.\n\n- When another MCP server already owns this server's name, the prompt shows a warning: \"Another MCP server owns this server's name.\" It explains that choosing \"Don't ask again\" moves the name, and the allow rules saved for it, to this server.\n\n- The always-allow option may now be shown even for tools that normally hide it. Before, `showAlwaysAllow` was blocked when the tool suppressed that rule.\n\n**Why**\n\nAllow rules are saved by server name. Without the warning, choosing \"Don't ask again\" could silently hand rules you gave one server to a different server. Read the warning before approving if two servers share a name.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}