Delete a single document by its ObjectId.
AI agents call delete_document_by_id to permanently remove resources in MongoDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from the database with no undo mechanism. Although it operates on a single document (limiting blast radius compared to bulk deletion), MongoDB deletions are irreversible. An AI agent given this tool could accidentally or maliciously delete critical records.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a single document by its ObjectId' — this is irreversible data removal.
Attacks that exploit this kind of access
Delete a single document by its ObjectId. It is categorised as a Destructive tool in the MongoDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MongoDB MCP Server MCP server in PolicyLayer and add a rule for delete_document_by_id: 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 MCP Server. Nothing to install.
delete_document_by_id 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_document_by_id 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_document_by_id. 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_document_by_id is provided by the MongoDB MCP Server MCP server (ruslankf777/mcp_mongo). 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 →