Delete a database user
AI agents call user_delete to permanently remove resources in MongoDB Atlas MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a database user account, which cannot be undone. Deletion is irreversible and has significant blast radius if invoked by an AI agent without proper authorization context. While not Financial in nature, it exceeds Execute severity due to the permanent loss of access control and potential operational disruption.
From the tool's definition Tool name is 'user_delete' and description states 'Delete a database user'. The delete operation is irreversible and represents permanent removal of a database user account.
Attacks that exploit this kind of access
Delete a database user. It is categorised as a Destructive tool in the MongoDB Atlas MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MongoDB Atlas 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 MongoDB Atlas 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 MongoDB Atlas MCP Server MCP server (montumodi/mongodb-atlas-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 →