The long-form docs for managedMcpServers' toolPolicy were rewritten and simplified. The previous documentation of an "ask-session" clamp — session-scoped "Allow for this task" tool approval with special wildcard precedence rules — no longer appears, and the wildcard precedence logic itself was simplified to remove the special ask-session case.
Names in the bundletoolPolicy
Documented inclaude-code/desktop
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Web search and web fetch touched a line naming toolPolicy after this was published.
Set the per-entry `toolPolicy` to `"allow"` so users aren't prompted to approve each search. `headersHelper` is an executable that prints the auth header as a JSON object to stdout; it follows the same execution model as [`inferenceCredent…third-party/claude-desktop/web-tools see the edit
Confirmed since
Anthropic's documentation has since written up toolPolicy, on MCP, plugins, skills, and hooks.
| `.mcp.json` | MCP servers bundled with this plugin. A JSON object keyed by server name: `{"mcpServers": {"<name>": {"type": "http", "url": "...", "oauth": true}}}`. A remote entry uses `type` (`http` or `sse`), not `transport`, and suppo…third-party/claude-desktop/extensions see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up toolPolicy, on MCP, plugins, skills, and hooks.
Anthropic's release notes agree
Changed Claude apps gateway to also refuse to start, naming the field, when a desktop policy misspells a field in a nested object of a…