{"version":"2.1.290","anchor":"new-permission-prompt-reason-for-slash-containing-names-pass","canonical_anchor":"new-permission-prompt-reason-for-slash-containing-names-pass","heading":"Names with a slash passed to served MCP tools are checked first","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-permission-prompt-reason-for-slash-containing-names-pass","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Names with a slash passed to served MCP tools are checked first\n\nA call that gives one of the app's own MCP tools a name containing a slash is now checked before it runs, with its own explanation\n\n**Unclear.** It is not clear whether this check runs in every case or only under certain conditions.\n\n**What**\n\nMCP (Model Context Protocol) is the standard way programs offer Claude tools. When a call gives one of the app's own MCP tools a name containing a slash or backslash, Claude Code now checks the call before it runs and explains why in the permission prompt. The explanation reads: \"This call gives one of [the app]'s own MCP tools a name with a slash in it, so it is checked before it runs.\"\n\nNames that are clearly a full path, a home-folder path, a variable or a web address are not matched by this rule. They already had their own explanations.\n\n**Why**\n\nRelative paths, such as `src\/file.txt`, passed to these tools now lead to a check and a clear reason, so they cannot slip through without notice.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}