What
allowManagedPermissionRulesOnly is a managed setting, one an organization's administrators set, that makes managed settings the only source of permission rules. A plugin can declare allowed-tools, a list of tools it may use without asking. The setting's description now says that under this setting a plugin keeps its allowed-tools only if it came through an admin-backed channel:
- plugins loaded with
--plugin-dirby the host - the official marketplace from its unpinned Anthropic source
- attested plugins synced from claude.ai
- the organization's claude.ai-hosted marketplaces
- marketplaces declared by managed
extraKnownMarketplacesor pinned bystrictKnownMarketplaces - registry-pinned plugins installed directly from npm
Every other plugin's allowed-tools are ignored. Before, the description said only plugins picked up from a plugin manifest inside user, project or added skills folders lost theirs.
Why
Organizations using this lockdown may find that plugins from ordinary marketplaces stop getting their tool permissions unless an admin vouches for where they came from.
Names in the bundleallowManagedPermissionRulesOnly
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Only the setting's description changed visibly; the code that enforces it was not seen.
Anthropic's release notes agree
Fixed plugins from marketplaces, claude.ai and npm pre-approving their own tools via allowed-tools under managed…