remove_xo_app
AI agents call remove_xo_app to permanently remove resources in XO MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'remove_xo_app' strongly suggests permanent deletion of applications from the XO platform. Although the description is empty (lowering confidence slightly), the name paired with the server's role in 'application lifecycle management' and 'container deployment' indicates this performs an irreversible action that cannot be undone. Misuse could result in loss of running applications and associated data.
From the tool's definition Tool name 'remove_xo_app' combined with server context showing application lifecycle management on XO infrastructure. The verb 'remove' in the context of application deployment indicates irreversible deletion of deployed applications.
Attacks that exploit this kind of access
remove_xo_app. It is categorised as a Destructive tool in the XO MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the XO MCP Server MCP server in PolicyLayer and add a rule for remove_xo_app: 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 XO MCP Server. Nothing to install.
remove_xo_app 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 remove_xo_app 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 remove_xo_app. 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.
remove_xo_app is provided by the XO MCP Server MCP server (sharmasuraj0123/xo-mcp-server). 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 →