Under the hood
A permission-prompt tool named none now routes through an ask-based fallback resolver instead of the MCP prompt tool.
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.