Alias for remove_app() using app wording.
AI agents call delete_app to permanently remove resources in PlugLayer MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an app is an irreversible action that removes application infrastructure and data. The tool name explicitly uses 'delete', which is a destructive operation. Given the infrastructure management context (deploying/managing infrastructure via natural language), misuse could result in loss of running applications and associated data.
From the tool's definition Tool name 'delete_app' and description 'Alias for remove_app()' indicate permanent removal of an application. Sibling tools include 'delete_database', 'delete_deployment', and 'delete_project', confirming this server handles destructive operations.
Attacks that exploit this kind of access
Alias for remove_app() using app wording. It is categorised as a Destructive tool in the PlugLayer MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for delete_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 PlugLayer MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_app is provided by the PlugLayer MCP Server MCP server (pluglayer/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 →