Delete a user
AI agents call delete-user to permanently remove resources in NestJS MCP Server Module — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a user account is an irreversible operation that destroys data and user records. This is the most severe category (Destructive > Execute > Write > Read). The critical severity reflects the high blast radius: an AI agent invoking this without proper authorization or by mistake would permanently remove a user account, affecting authentication, data access, and system integrity.
From the tool's definition Tool name 'delete-user' and description 'Delete a user' explicitly indicate irreversible deletion of user data. The verb 'delete' is a clear destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a user. It is categorised as a Destructive tool in the NestJS MCP Server Module MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NestJS MCP Server Module 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 NestJS MCP Server Module. Nothing to install.
delete-user 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 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. 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 is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). 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 →