Your organisation has set one tool on a shared connector to require approval. You add an allow rule for it locally so your own sessions stop asking. What happens next time you use it?

The principle — Local configuration expresses a preference. Organisational policy expresses a requirement, and a requirement a user can switch off is not one.

Why the key is correct — When an organisation sets a connector tool to ask, Claude Code prompts on every call with the reason that your organisation requires approval for this tool. The prompt appears in the permissive modes as well, and allow rules that match the tool do not skip it.

Why the others are wrong — The local rule does not win, because specificity is not the axis here. The control does not exempt people who have set rules. And no dismissal is offered, however well you understand the reason.

Remember this — When the prompt names your organisation, no local rule will remove it. The setting is enforced locally but decided elsewhere, so the only route to changing it runs through whoever administers the connector.

Sources — Anthropic's Claude Code MCP reference.