zitadel_lock_user

THE RISK

Medium Risk

Why zitadel_lock_user needs a policy

Locking a user account changes their authentication state but does not delete or destroy data. It is reversible via an unlock operation, distinguishing it from Destructive. The action impacts a user's ability to access the system, creating significant operational impact (high severity), but is not financial or permanently damaging. The requirement for 'confirm: true' indicates awareness of the sensitivity.

From the tool's definition 'Lock a user account. The user will not be able to log in until unlocked.' — this modifies user state by disabling login capability, which is reversible (unlocking restores access).

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

POLICY

How to control zitadel_lock_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_lock_user:

policy.json

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

zitadel_lock_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 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.

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_lock_user

What does the zitadel_lock_user tool do? +

Lock a user account. The user will not be able to log in until unlocked. Requires confirm: true. 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_lock_user? +

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

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

Can I rate-limit zitadel_lock_user? +

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

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

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