mcp_drop_collection

A destructive tool on the Mongo- MCP server.

SERVERMongo-MCP SOURCE441126098/mongo-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/441126098-mongo-mcp/mcp-drop-collection.md

WHAT IT DOES

What mcp_drop_collection does on Mongo-MCP

AI agents call mcp_drop_collection to permanently remove resources in Mongo-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mcp_drop_collection is rated Critical

Dropping a collection irreversibly deletes all data and indexes within it. This is a classic Destructive operation that cannot be undone without a backup. The tool's name alone ('drop_collection') is explicit enough to classify with high confidence despite the empty description. Given the critical data loss potential, severity is critical.

From the tool's definition Tool name 'mcp_drop_collection' with verb 'drop' indicates irreversible deletion of an entire MongoDB collection. The server description confirms this tool is part of CRUD and administrative operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_drop_collection safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mongo-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_drop_collection, this is the rule to start with:

mcp_drop_collection Hidden

mcp_drop_collection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mcp_drop_collection"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mongo-MCP, apply this rule, and every mcp_drop_collection call is checked against it from then on.

FAQ

Questions about mcp_drop_collection

What does the mcp_drop_collection tool do? +

mcp_drop_collection is a destructive tool on the Mongo MCP server. It is categorised as a Destructive tool in the Mongo-MCP 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 mcp_drop_collection? +

Register the Mongo MCP server in PolicyLayer and add a rule for mcp_drop_collection: 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 Mongo-MCP. Nothing to install.

What risk level is mcp_drop_collection? +

mcp_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 mcp_drop_collection? +

Yes. Add a rate_limit block to the mcp_drop_collection 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.

How do I block mcp_drop_collection completely? +

Set action: deny in the PolicyLayer policy for mcp_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 mcp_drop_collection? +

mcp_drop_collection is provided by the Mongo MCP server (441126098/mongo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mongo, and thousands of servers like it.

This server

All 30 Mongo tools → Critical-risk tools on this server →

Across the catalogue

reset_mcp_runtime_metrics on 0xpdf →clear_collection on MCP RAG Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →