xano_delete_api_group
AI agents call xano_delete_api_group 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 operations that remove organizational structures, configurations, or resources cannot be undone and qualify as Destructive. Even without a detailed description, the explicit 'delete' action on a named resource (api_group) indicates irreversible data/configuration loss. Confidence is slightly reduced due to empty description, but the tool name itself provides sufficient evidence.
From the tool's definition Tool name 'xano_delete_api_group' indicates deletion of an API group resource. The 'delete' verb combined with 'api_group' scope suggests irreversible removal of infrastructure/configuration.
Attacks that exploit this kind of access
xano_delete_api_group. 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_group: 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_group 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_group 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_group. 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_group 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.
xano_delete_api_group is one line of Xano MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →