Delete user by id.
AI agents call user_delete to permanently remove resources in Database MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes user records from the database. Deletion of user data is a destructive operation with potentially severe consequences (data loss, account termination, compliance violations). While not as critical as some destructive operations that might cascade (e.g., deleting entire tables), deleting individual users by ID is still a high-severity destructive action.
From the tool's definition Tool name 'user_delete' combined with description 'Delete user by id' explicitly performs irreversible deletion of data. The verb 'delete' is characteristic of destructive operations that cannot be undone.
Attacks that exploit this kind of access
Delete user by id. It is categorised as a Destructive tool in the Database MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for user_delete: 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 Database MCP Server. Nothing to install.
user_delete 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 user_delete 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 user_delete. 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.
user_delete is provided by the Database MCP Server MCP server (vrushil1/database-mcp). 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 →