xano_bulk_delete_files
AI agents call xano_bulk_delete_files 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.
Bulk deletion operations are inherently destructive—they remove data that cannot be recovered without external backups. Combined with 'bulk' scope, a single invocation can affect many files simultaneously, creating a large blast radius. Even with responsible input validation, an agent error (e.g., wrong filter criteria) could destroy significant data.
From the tool's definition Tool name 'xano_bulk_delete_files' contains 'bulk_delete', which indicates irreversible deletion of multiple files in a Xano database. The tool description is empty, preventing direct textual confirmation, but the naming convention is unambiguous.
Attacks that exploit this kind of access
xano_bulk_delete_files. 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_bulk_delete_files: 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_bulk_delete_files 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_bulk_delete_files 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_bulk_delete_files. 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_bulk_delete_files 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 →