mcp_delete_document
A destructive tool on the Mongo- MCP server.
This record as markdown: /tools/441126098-mongo-mcp/mcp-delete-document.md
What mcp_delete_document does on Mongo-MCP
AI agents call mcp_delete_document to permanently remove resources in Mongo-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mcp_delete_document is rated Critical
The tool name unambiguously indicates document deletion in MongoDB. Deletions are irreversible operations that cannot be undone without restoring from backups. Even though the description is empty, the name alone is sufficiently explicit to classify this as Destructive rather than Write. An AI agent with access to this tool could permanently lose data if misused.
From the tool's definition Tool name is 'mcp_delete_document' which explicitly performs deletion. MongoDB delete operations are irreversible.
Attacks that exploit this kind of access
The rule that runs mcp_delete_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mongo-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_delete_document, this is the rule to start with:
mcp_delete_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mongo-MCP, apply this rule, and every mcp_delete_document call is checked against it from then on.
Questions about mcp_delete_document
mcp_delete_document is a destructive tool on the Mongo MCP server. It is categorised as a Destructive tool in the Mongo-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mongo MCP server in PolicyLayer and add a rule for mcp_delete_document: 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 Mongo-MCP. Nothing to install.
mcp_delete_document 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 mcp_delete_document 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 mcp_delete_document. 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.
mcp_delete_document is provided by the Mongo MCP server (441126098/mongo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mongo, and thousands of servers like it.
Across the catalogue