Critical Risk →

drop-collection

Removes a collection or view from the database. The method also removes any indexes associated with the dropped collection.

Part of the MongoDB MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@mongodb-js/mongodb-mcp-server Destructive Risk 4/5

AI agents may call drop-collection to permanently remove or destroy resources in MongoDB. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call drop-collection in a loop, permanently destroying resources in MongoDB. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

mongodb.yaml
tools:
  drop-collection:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full MongoDB policy for all 29 tools.

Tool Name drop-collection
Category Destructive
MCP Server MongoDB MCP Server
Risk Level Critical

View all 29 tools →

Agents calling destructive-class tools like drop-collection have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

drop-collection is one of the critical-risk operations in MongoDB. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the drop-collection tool do? +

Removes a collection or view from the database. The method also removes any indexes associated with the dropped collection.. It is categorised as a Destructive tool in the MongoDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on drop-collection? +

Add a rule in your Intercept YAML policy under the tools section for drop-collection. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MongoDB MCP server.

What risk level is drop-collection? +

drop-collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drop-collection? +

Yes. Add a rate_limit block to the drop-collection rule in your Intercept 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.

How do I block drop-collection completely? +

Set action: deny in the Intercept policy for drop-collection. 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.

What MCP server provides drop-collection? +

drop-collection is provided by the MongoDB MCP server (@mongodb-js/mongodb-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on MongoDB

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.