Delete records from a table. Filters are REQUIRED — use truncate to remove all rows.
AI agents call delete to permanently remove resources in MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete tool irreversibly removes data from a database table. Although the requirement for filters prevents accidental bulk deletion of all rows, individual or batch deletions cannot be undone without database backups or transaction rollback. This causes permanent data loss and qualifies as Destructive rather than Write (which is reversible).
From the tool's definition The tool permanently deletes records from a table. The description explicitly states it removes rows ("Delete records from a table") and directs users to truncate for removing all rows, confirming this is an irreversible data deletion operation.
Attacks that exploit this kind of access
Delete records from a table. Filters are REQUIRED — use truncate to remove all rows. It is categorised as a Destructive tool in the MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for 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 MySQL MCP Server. Nothing to install.
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 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 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.
delete is provided by the MySQL MCP Server MCP server (zoherr/mysql-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 →