zitadel_reactivate_user

THE RISK

Medium Risk

Why zitadel_reactivate_user needs a policy

This tool reverses a deactivation, restoring a user account to active status. It is a reversible state change (Write), not a deletion or irreversible action. Misuse could grant unintended access to previously disabled accounts, making severity medium.

From the tool's definition Reactivate a previously deactivated user account

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

POLICY

How to control zitadel_reactivate_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_reactivate_user:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zitadel_reactivate_user": {
      "limits": [
        {
          "counter": "zitadel_reactivate_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

zitadel_reactivate_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT 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. Destructive zitadel_deactivate_user Deactivate a user account. The user will no longer be able to log in. Requires confirm: tr 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about zitadel_reactivate_user

What does the zitadel_reactivate_user tool do? +

Reactivate a previously deactivated user account. It is categorised as a Write tool in the Zitadel MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zitadel_reactivate_user? +

Register the Zitadel MCP server in PolicyLayer and add a rule for zitadel_reactivate_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_reactivate_user? +

zitadel_reactivate_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zitadel_reactivate_user? +

Yes. Add a rate_limit block to the zitadel_reactivate_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_reactivate_user completely? +

Set action: deny in the PolicyLayer policy for zitadel_reactivate_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_reactivate_user? +

zitadel_reactivate_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 →