Critical Risk →

DeleteUser

Delete the specified user

Risk signalsHandles credentials or secrets (auth)

Part of the Clerk server.

DeleteUser can permanently delete data in Clerk, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CLERK →

Free to start. No card required.

AI agents may call DeleteUser to permanently remove or destroy resources in Clerk. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call DeleteUser in a loop, permanently destroying resources in Clerk. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "DeleteUser"
  ]
}

See the full Clerk policy for all 14 tools.

Get this rule live on your own Clerk server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLERK →

View all 14 tools →

These attack patterns abuse exactly the kind of access DeleteUser gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so DeleteUser only ever does what you allow.

SECURE CLERK →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the DeleteUser tool do? +

Delete the specified user. It is categorised as a Destructive tool in the Clerk 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 DeleteUser? +

Register the Clerk MCP server in PolicyLayer and add a rule for DeleteUser: 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 Clerk. Nothing to install.

What risk level is DeleteUser? +

DeleteUser 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 DeleteUser? +

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

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

DeleteUser is provided by the Clerk MCP server (@clerk/clerk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clerk tool call.

Deterministic rules across all 14 Clerk tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.