delete_user

Delete a user from the org by id. This is permanent, removes org and workspace memberships, revokes API keys, and ends active sessions; use delete_user_invite for pending invites instead.

Server Portkey Admin CodesWhat/portkey-admin-mcp
Category Destructive
Risk class Critical
Parameters 11 required

What delete_user does on Portkey Admin

AI agents call delete_user to permanently remove resources in Portkey Admin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
user_id string Yes The user ID to delete

Parameters from the server's own tool schema.

Why delete_user needs a policy

An AI agent that decides to call delete_user doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Portkey Admin is gone — there is no undo for destructive operations.

Questions about delete_user

What does the delete_user tool do? +

Delete a user from the org by id. This is permanent, removes org and workspace memberships, revokes API keys, and ends active sessions; use delete_user_invite for pending invites instead. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_user accept? +

delete_user accepts 1 parameter: user_id. Required: user_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_user? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for delete_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 Portkey Admin. Nothing to install.

What risk level is delete_user? +

delete_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 delete_user? +

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

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

delete_user is provided by the Portkey Admin MCP server (CodesWhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.