Delete all documents matching a filter
AI agents call delete-many to permanently remove resources in Mongodb3 — 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 undo. The use of 'Delete all documents' combined with a filter parameter indicates bulk deletion capability. While not financial, this is severely destructive as it can wipe entire collections or subsets thereof depending on filter specification.
From the tool's definition Tool name 'delete-many' and description 'Delete all documents matching a filter' explicitly perform irreversible deletion of potentially large numbers of documents from MongoDB.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete all documents matching a filter. It is categorised as a Destructive tool in the Mongodb3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mongodb3 MCP server in PolicyLayer and add a rule for 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 Mongodb3. Nothing to install.
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 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 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.
delete-many is provided by the Mongodb3 MCP server (mongodb3-mcp-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 →