zitadel_deactivate_user

THE RISK

Critical Risk

Why zitadel_deactivate_user needs a policy

Deactivating a user account revokes their ability to authenticate, which is a significant irreversible-in-effect action (even if technically re-activatable, it locks the user out immediately). The requirement for 'confirm: true' signals this is a high-impact, potentially irreversible operation. Misuse could lock out legitimate users or administrators, making it Destructive with high severity.

From the tool's definition Deactivate a user account. The user will no longer be able to log in.

Documented attack patterns abuse exactly the kind of access zitadel_deactivate_user gives an agent:

POLICY

How to control zitadel_deactivate_user

PolicyLayer is an MCP gateway — it sits between your AI agents and Zitadel MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for zitadel_deactivate_user:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "zitadel_deactivate_user"
  ]
}

zitadel_deactivate_user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Zitadel MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zitadel MCP tools

Destructive zitadel_delete_user Permanently delete a user. This action cannot be undone. Requires confirm: true. Consider Destructive zitadel_remove_user_grant Remove a role grant from a user by grant ID. Requires confirm: true. Write zitadel_reactivate_user Reactivate a previously deactivated user account. Write portal_register_app Register an application in the app-portal database so it appears in the portal UI. This on Write portal_setup_full_app One-click app setup: creates a Zitadel project (or uses existing), OIDC application, proje Write zitadel_create_oidc_app Create a new OIDC application in a Zitadel project. Returns the Client ID (and Client Secr Write zitadel_create_project Create a new project in Zitadel. Projects contain applications, roles, and grants. Write zitadel_create_service_user Create a new service account (machine user) for API access. Service accounts authenticate

All 26 Zitadel MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Zitadel MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about zitadel_deactivate_user

What does the zitadel_deactivate_user tool do? +

Deactivate a user account. The user will no longer be able to log in. Requires confirm: true. It is categorised as a Destructive tool in the Zitadel MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on zitadel_deactivate_user? +

Register the Zitadel MCP server in PolicyLayer and add a rule for zitadel_deactivate_user: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Zitadel MCP. Nothing to install.

What risk level is zitadel_deactivate_user? +

zitadel_deactivate_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit zitadel_deactivate_user? +

Yes. Add a rate_limit block to the zitadel_deactivate_user rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block zitadel_deactivate_user completely? +

Set action: deny in the PolicyLayer policy for zitadel_deactivate_user. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides zitadel_deactivate_user? +

zitadel_deactivate_user is provided by the Zitadel MCP server (takleb3rry/zitadel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zitadel MCP tool call.

Start from Zitadel MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →