Drop a database and all its collections
AI agents call drop-database to permanently remove resources in Mongodb3 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible destructive operation that cannot be undone. Dropping a database permanently deletes all collections and data within it. This represents the highest severity risk as it could result in total data loss across an entire database. An AI agent misusing this tool could catastrophically destroy all data managed by that MongoDB instance, making it critical severity.
From the tool's definition Tool name 'drop-database' combined with description 'Drop a database and all its collections' explicitly indicates irreversible deletion of all data within a database.
Attacks that exploit this kind of access
Drop a database and all its collections. It is categorised as a Destructive tool in the Mongodb3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mongodb3 MCP server in PolicyLayer and add a rule for drop-database: 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 Mongodb3. Nothing to install.
drop-database 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 drop-database 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 drop-database. 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.
drop-database is provided by the Mongodb3 MCP server (mongodb3-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 →