Critical Risk →

drop-database

Removes the specified database, deleting the associated data files

Part of the MongoDB server.

drop-database can permanently delete data in MongoDB, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MONGODB →

Free to start. No card required.

AI agents may call drop-database 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. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call drop-database in a loop, permanently destroying resources in MongoDB. There is no undo for destructive operations. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "drop-database"
  ]
}

See the full MongoDB policy for all 29 tools.

Get this rule live on your own MongoDB server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MONGODB →

View all 29 tools →

These attack patterns abuse exactly the kind of access drop-database gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so drop-database only ever does what you allow.

SECURE MONGODB →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the drop-database tool do? +

Removes the specified database, deleting the associated data files. 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-database? +

Register the MongoDB 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 MongoDB. Nothing to install.

What risk level is drop-database? +

drop-database 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-database? +

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.

How do I block drop-database completely? +

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.

What MCP server provides drop-database? +

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

Enforce policy on every MongoDB tool call.

Deterministic rules across all 29 MongoDB tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.