{"version":"2.1.259","anchor":"permission-prompt-tool-routing-gets-a-bypass-for-an-explicit","canonical_anchor":"permission-prompt-tool-routing-gets-a-bypass-for-an-explicit","heading":"Permission-prompt-tool routing gets a bypass for an explicit \"none\" sentinel","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/permission-prompt-tool-routing-gets-a-bypass-for-an-explicit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Permission-prompt-tool routing gets a bypass for an explicit \"none\" sentinel\n\nA permission-prompt tool named none now routes through an ask-based fallback resolver instead of the MCP prompt tool.\n\n`canUseTool` construction now checks whether the permission-prompt-tool server name is the literal sentinel `\"none\"`. When it is, or when no MCP prompt tool was configured, requests can go through an ask-based fallback path that resolves `ask` behaviors via a new resolver before falling through to normal permission-denied handling.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}