Delete a specific record from a table.
AI agents call xano_delete_table_record to permanently remove resources in Xano MCP Server for Smithery — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes data from a database table. Deletion cannot be undone without manual recovery procedures (if available), making this a destructive operation rather than merely a write operation. Given that it operates on database records in a production context (Xano), the severity is high due to potential data loss impact.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a specific record from a table.' This is an irreversible data removal operation.
Attacks that exploit this kind of access
Delete a specific record from a table. It is categorised as a Destructive tool in the Xano MCP Server for Smithery MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xano MCP Server for Smithery 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 for Smithery. 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 for Smithery MCP server (roboulos/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 →