Delete documents from a MongoDB collection
AI agents call mongodb_delete to permanently remove resources in MCP-MongoDB-MySQL-Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool directly deletes data from a MongoDB collection, which is an irreversible operation that cannot be undone through the tool itself. This qualifies as Destructive rather than Write (which is reversible). The high severity reflects the potential for significant data loss if an AI agent misuses this tool without proper safeguards, especially in production environments.
From the tool's definition Tool name 'mongodb_delete' combined with description 'Delete documents from a MongoDB collection' indicates irreversible removal of data. MongoDB delete operations remove documents permanently unless backups exist.
Documented attack patterns abuse exactly the kind of access mongodb_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-MongoDB-MySQL-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mongodb_delete:
{
"version": "1",
"default": "deny",
"hide": [
"mongodb_delete"
]
} mongodb_delete 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.
Delete documents from a MongoDB collection. It is categorised as a Destructive tool in the MCP-MongoDB-MySQL-Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-MongoDB-MySQL-Server MCP server in PolicyLayer and add a rule for mongodb_delete: 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-MongoDB-MySQL-Server. Nothing to install.
mongodb_delete 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 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. 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 is provided by the MCP-MongoDB-MySQL-Server MCP server (yaoxiaolinglong/mcp-mongodb-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-MongoDB-MySQL-Server, 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.
14 MCP-MongoDB-MySQL-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.