xano_delete_table_record
AI agents call xano_delete_table_record 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.
Deletion of database records is irreversible and cannot be undone. This falls into the Destructive category, which takes precedence over Write. Severity is high because deleting individual records can corrupt data integrity and cause significant harm depending on the database's role, though the blast radius is somewhat limited compared to bulk operations like xano_bulk_delete_records. Confidence is 0.9 rather than 1.
From the tool's definition Tool name 'xano_delete_table_record' explicitly indicates deletion of a database record. No description provided, but the name unambiguously describes a destructive operation on stored data.
Attacks that exploit this kind of access
xano_delete_table_record. 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_delete_table_record: 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_delete_table_record 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_delete_table_record 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_delete_table_record. 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_delete_table_record 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 →