Administrator-managed settings can now block plugins and marketplaces whose entry source is not listed in the managed extraKnownMarketplaces policy, so install, update and refresh stop with a policy error instead of running that entry's command for minting auth headers. Refusals are reported separately from ordinary failures, and the messages name the policy rather than looking like a network or catalog fault. Nothing is blocked unless the managed policy sets disableCommandPluginSources or allowManagedHooksOnly; without those, behaviour is unchanged.
- A blocked marketplace update reports
<name> marketplace not updated (managed policy) — ask your adminand lists the sources that were refused. - The plugin update path explains that
your organization's managed settings forbid its headersHelper (the version shown is from the cached catalog; ask your admin), so the displayed version may be stale. - Each refusal is classified as either "lockdown", meaning the policy forbids the source outright, or "remote_policy_unconsented", meaning a remote source whose policy has not been consented to in the current remote session.
- Two new diagnostic kinds carry these refusals, including an
autoupdate-disabled-by-policynotice. - Refused marketplaces are gathered into their own list during refresh rather than folded in with genuine failures.
headersHelper, the command that supplies auth headers for a source, is now accepted on plugin entries declared in settings files as well as on marketplace entries, and a validator rejects values that are over-long or contain non-printable ASCII.- The message for an inactive plugin no longer says "or blocked by policy" and now states only that the plugin is disabled.
autoupdate-disabled-by-policy, not updated (managed policy), your organization's managed settings forbid its headersHelper (the version shown is from the cached catalog; ask your admin)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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.
Claude Code [managed settings](/docs/third-party/claude-desktop/code#interaction-with-claude-code%E2%80%99s-own-managed-settings) deployed on the device govern these hooks as they do in the Claude Code CLI: `disableAllHooks` turns them off…third-party/claude-desktop/extensions see the edit
Anthropic's documentation has since written up allowManagedHooksOnly, on MCP, plugins, skills, and hooks.
Plugin marketplaces: headersHelper on a url marketplace or a catalog entry runs a command that mints HTTP headers (e.g. a short-lived token)…