xano_truncate_table
AI agents call xano_truncate_table to permanently remove resources in Xano 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 deletes all records from a table in a single irreversible action. This has the highest blast radius: an AI agent with access to this tool could wipe entire datasets with a single call. Even though the description is missing, the semantic meaning of 'truncate' in database contexts is clear and unambiguous, warranting critical severity and high confidence.
From the tool's definition Tool name is `xano_truncate_table`. Truncate is a SQL operation that irreversibly removes all rows from a table. The description is empty, but the name alone is unambiguous—truncate operations cannot be undone and result in permanent data loss.
Attacks that exploit this kind of access
xano_truncate_table. It is categorised as a Destructive tool in the Xano MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xano MCP Server MCP server in PolicyLayer and add a rule for xano_truncate_table: 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 Xano MCP Server. Nothing to install.
xano_truncate_table 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 xano_truncate_table 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 xano_truncate_table. 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.
xano_truncate_table is provided by the Xano MCP Server MCP server (roboulos/simple-xano-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 →