Remove ALL records from a table. This is irreversible. Requires confirm=true to execute.
AI agents call truncate 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.
TRUNCATE is a destructive operation that irreversibly removes all data from a table in a single action. While the requirement for confirm=true provides a friction layer, it does not prevent the operation itself. The blast radius is maximal—loss of an entire table's data—and recovery typically requires backups. This is unrecoverable data loss, making it the most severe category.
From the tool's definition Tool description explicitly states 'Remove ALL records from a table. This is irreversible.' The verb 'truncate' is a SQL TRUNCATE operation that permanently deletes all rows.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove ALL records from a table. This is irreversible. Requires confirm=true to execute. 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 truncate: 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.
truncate 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 truncate 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 truncate. 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.
truncate 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 →