xano_delete_api
AI agents call xano_delete_api 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.
The 'delete' verb combined with 'api' as the target indicates this tool performs irreversible deletion of API configurations in Xano. Deletion of APIs cannot be undone and would break dependent integrations and workflows. Though the description is empty (lowering confidence slightly), the name and context of sibling destructive tools make this categorization clear.
From the tool's definition Tool name 'xano_delete_api' indicates deletion of an API configuration. Given the sibling tools include 'xano_bulk_delete_records' and 'xano_bulk_delete_files' (clearly destructive), and this tool targets API deletion rather than data, it represents…
Attacks that exploit this kind of access
xano_delete_api. 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_api: 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_api 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_api 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_api. 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_api 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 →