AI agents call mysql_delete to permanently remove resources in Db — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
MySQL DELETE is a destructive operation that permanently removes records from a database. While the server mentions 'runtime protections' and 'graded security modes' which may mitigate some risk, the fundamental capability is irreversible data deletion. This is more severe than Write (which is reversible) and ranks as Destructive.
From the tool's definition Tool name explicitly states 'delete' and description confirms '执行 MySQL DELETE 删除操作' (executes MySQL DELETE operation). DELETE operations irreversibly remove data from database rows.
Documented attack patterns abuse exactly the kind of access mysql_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_delete:
{
"version": "1",
"default": "deny",
"hide": [
"mysql_delete"
]
}mysql_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.
执行 MySQL DELETE 删除操作。若服务启动时已预配置 MySQL，会直接使用默认连接。. It is categorised as a Destructive tool in the Db MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Db MCP server in PolicyLayer and add a rule for mysql_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 Db. Nothing to install.
mysql_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 mysql_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 mysql_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.
mysql_delete is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, 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.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.