AI agents call delete-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.
Deleting a table destroys all data within it and cannot be undone. This is a classic destructive operation with high blast radius if an AI agent invokes it unintentionally or based on a misunderstood user request. It outranks Write (reversible modifications) and is the most severe category applicable.
From the tool's definition Tool name is 'delete-table' and description states 'Delete a table from the Xano workspace'. The verb 'delete' combined with the scope (entire table) indicates irreversible data removal.
Documented attack patterns abuse exactly the kind of access delete-table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xano MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-table:
{
"version": "1",
"default": "deny",
"hide": [
"delete-table"
]
} delete-table disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a table from the Xano workspace. 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 delete-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.
delete-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 delete-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 delete-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.
delete-table is provided by the Xano MCP Server MCP server (lowcodelocky2/xano-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xano MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Xano MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.