Delete data from a table.
AI agents call delete_data to permanently remove resources in MCP MySQL 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 a database table with no built-in undo mechanism. Even though the tool appears parameterized (targeting specific tables), deletion operations are inherently irreversible and represent the highest risk category. An AI agent instructed to 'clean up old records' or given ambiguous deletion criteria could destroy critical data. The blast radius is maximum: data loss is permanent.
From the tool's definition Tool name is 'delete_data' and description explicitly states 'Delete data from a table.' The server description also mentions the tool is part of a system with 'comprehensive SQL execution capabilities' that supports 'data manipulation' and 'table management'.
Attacks that exploit this kind of access
Delete data from a table. It is categorised as a Destructive tool in the MCP MySQL Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for delete_data: 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 MySQL Server. Nothing to install.
delete_data 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_data 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_data. 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_data is provided by the MCP MySQL Server MCP server (kami2k1/mcp-mysql). 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 →