Delete multiple documents from a MongoDB collection
AI agents call mongo_delete_many to permanently remove resources in Mcp Database — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data without the ability to undo the operation, matching the Destructive category definition. The severity is high because a single misuse could delete many documents at once, causing significant data loss. Confidence is very high because the intent is unambiguous from both the name and description.
From the tool's definition Tool name 'mongo_delete_many' explicitly performs deletion ('delete') of 'multiple documents' from a MongoDB collection, which is an irreversible operation that permanently removes data.
Attacks that exploit this kind of access
Delete multiple documents from a MongoDB collection. It is categorised as a Destructive tool in the Mcp Database MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Database MCP server in PolicyLayer and add a rule for mongo_delete_many: 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 Mcp Database. Nothing to install.
mongo_delete_many 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 mongo_delete_many 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 mongo_delete_many. 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.
mongo_delete_many is provided by the Mcp Database MCP server (nam088/mcp-database-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 →