You'll notice
The built-in WebSearch tool now has an explicit permission check that suggests adding an allow rule
What
The built-in WebSearch tool now has its own checkPermissions method. When permission hasn't been granted, it returns a 'passthrough' result with the message "WebSearchTool requires permission." and suggests adding an allow rule for the WebSearch tool to your local settings.
Why
This gives WebSearch its own explicit, self-describing permission check rather than relying on generic handling, and points users toward the specific settings change needed to allow it going forward.
Names in the bundleWebSearch
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 Test plugins with evals touched a line naming WebSearch after this was published.
Runs never stop to ask for permission. Built-in tools that need a grant you didn't give, such as `Bash`, `Write`, `Edit`, `WebFetch`, and `WebSearch`, are removed from the session, so Claude can't call them at all.plugin-evals see the edit
Confirmed since
Anthropic's documentation has since written up WebSearch, on Configuration reference.
| <span id="disablebundledskills" />Disable bundled skills and workflows<br />`disableBundledSkills` | `boolean` | MDM + Bootstrap<br />Added in 1.15962.0 | — | Disables Claude Code’s bundled skills and workflows (deep-research and similar…third-party/claude-desktop/configuration see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up WebSearch, on Configuration reference.