{"version":"2.1.251","anchor":"mcp-tools-no-longer-blocked-by-a-name-clash-with-a-built-in-","canonical_anchor":"mcp-tools-no-longer-blocked-by-a-name-clash-with-a-built-in-","heading":"MCP tools no longer blocked by a name clash with a built-in tool","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/mcp-tools-no-longer-blocked-by-a-name-clash-with-a-built-in-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### MCP tools no longer blocked by a name clash with a built-in tool\n\nAn MCP tool sharing a name with a built-in tool is no longer silently blocked.\n\n**What**\n\nA tool provided by an MCP server is now treated as enabled if a built-in tool of the same name is enabled, closing a case where a name collision could silently block the MCP tool despite permissions allowing it.\n\n**Details**\n\n- Unconditional.\n\n**Evidence**\n\n`n.mcpInfo === void 0`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}