Delete a single user by their numeric ID
AI agents call delete-user-by-id to permanently remove resources in Users — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user data from the system with no ability to undo the operation. Deletion is irreversible and constitutes a destructive action. While the blast radius is limited to a single user record, the action cannot be reversed, making it more severe than Write operations. High severity because an agent with misused access could permanently remove valid user accounts.
From the tool's definition Tool name 'delete-user-by-id' with description 'Delete a single user by their numeric ID' explicitly performs deletion of user records irreversibly.
Attacks that exploit this kind of access
Delete a single user by their numeric ID. It is categorised as a Destructive tool in the Users MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Users MCP server in PolicyLayer and add a rule for delete-user-by-id: 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 Users. Nothing to install.
delete-user-by-id is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-user-by-id 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.
Set action: deny in the PolicyLayer policy for delete-user-by-id. 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.
delete-user-by-id is provided by the Users MCP server (stormdotcom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →