从表中删除数据
AI agents call delete_data to permanently remove resources in MySQL MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of database records. Unlike Write operations that modify data reversibly, delete_data cannot be undone without external backups. Even with transaction rollback capability, the primary intent and effect is destructive data loss. Given the database context and direct access to delete rows, misuse could result in permanent loss of critical business data.
From the tool's definition Tool name 'delete_data' and description '从表中删除数据' (delete data from table) indicate irreversible data removal. The verb 'delete' is a core destructive operation that removes records from a database without recovery capability.
Attacks that exploit this kind of access
从表中删除数据. It is categorised as a Destructive tool in the MySQL MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MySQL 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 MySQL MCP. 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 MySQL MCP server (liu-creators/mysql-mcp). 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 →