AI agents call mongodb_delete_one to permanently remove resources in Db — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without possibility of recovery (barring backups). Although it operates on a single document rather than bulk deletion, it is irreversible and destructive by nature. Severity is 'high' rather than 'critical' because the blast radius is limited to a single document, but the operation is categorically Destructive per the classification rules.
From the tool's definition Tool name 'mongodb_delete_one' and description indicating deletion of a single document from a MongoDB collection.
Documented attack patterns abuse exactly the kind of access mongodb_delete_one gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for mongodb_delete_one:
{
"version": "1",
"default": "deny",
"hide": [
"mongodb_delete_one"
]
}mongodb_delete_one disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
删除 MongoDB 集合中的单个文档. It is categorised as a Destructive tool in the Db MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Db MCP server in PolicyLayer and add a rule for mongodb_delete_one: 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 Db. Nothing to install.
mongodb_delete_one 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 mongodb_delete_one 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 mongodb_delete_one. 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.
mongodb_delete_one is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.