You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
Unclear The rule is stated in the settings descriptions, and where Claude Code enforces it is not settled.
What
allowManagedPermissionRulesOnly is a managed setting. Managed settings are pushed by an organisation's administrators, and this one makes them the only place permission rules can come from. When it is set, the settings now describe an extra condition for plugin marketplaces. A marketplace is a catalogue that plugins are installed from.
Marketplace source: a marketplace defined in settings keeps its plugins' allowed-tools only when every npm entry pins a registry on a bare package name. Allowed-tools is the list of tools a plugin may use without asking.
Registry field: an npm marketplace keeps plugin allowed-tools only when the policy entry and the marketplace registration both pin the same registry.
While the setting is on, marketplace sync also downloads the marketplace again every time. It no longer skips the download when the server reports that nothing has changed.
Why
Administrators who rely on npm-sourced plugin marketplaces can lose those plugins' tool grants unless they pin a registry. Check your managed configuration if plugins stop getting the tools they had before.
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.
Confirmed sinceAnthropic's documentation has since written up allowManagedPermissionRulesOnly, on Extend Claude with skills.* The frontmatter applies in every kind of session, so an `allowed-tools` grant goes through the normal [permission flow](/docs/en/permissions). If your organization sets `allowManagedPermissionRulesOnly`, the grant [doesn't apply](#when-o…skillssee the edit
Added sinceA small documentation edit on Extend agents with skills touched a line naming allowManagedPermissionRulesOnly after this was published.In SDK sessions, you can pre-approve tools for a project or personal skill with the skill's [`allowed-tools`](/docs/en/skills#pre-approve-tools-for-a-skill) frontmatter or with the `allowedTools` option (`allowed_tools` in Python) in your …agent-sdk/skillssee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe rule is stated in the settings descriptions, and where Claude Code enforces it is not settled.
Anthropic's documentation agreesA small documentation edit on Extend agents with skills touched a line naming allowManagedPermissionRulesOnly after this was published.
Anthropic's release notes agreeFixed plugins from marketplaces, claude.ai and npm pre-approving their own tools via allowed-tools under managed…
