Drop an entire collection
AI agents call dropCollection to permanently remove resources in MongoDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes all data in a collection with no undo capability. Given the MongoDB context where collections can contain millions of records, this represents maximum blast radius and data loss risk. Destructive is the correct category per the severity hierarchy, and critical severity is appropriate for permanent data destruction at scale.
From the tool's definition Tool name 'dropCollection' and description 'Drop an entire collection' explicitly indicate permanent deletion of an entire MongoDB collection and all its data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Drop an entire collection. It is categorised as a Destructive tool in the MongoDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MongoDB MCP Server MCP server in PolicyLayer and add a rule for dropCollection: 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 MCP Server. Nothing to install.
dropCollection 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 dropCollection 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 dropCollection. 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.
dropCollection is provided by the MongoDB MCP Server MCP server (ryaker/mongodb-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 →