delete_application
Delete a deployed runtime application
This record as markdown: /tools/cbrown35-20i-mcp/delete-application.md
What delete_application does on 20i MCP Server
AI agents call delete_application to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_application is rated Critical
The tool performs deletion of deployed applications, which is an irreversible action that cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While not as critical as deleting customer data wholesale, removing a deployed application causes immediate service disruption and data loss for that application.
From the tool's definition Tool name includes 'delete' and description states 'Delete a deployed runtime application' - this is an irreversible operation that removes deployed application infrastructure.
Attacks that exploit this kind of access
The rule that runs delete_application safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_application, this is the rule to start with:
delete_application is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every delete_application call is checked against it from then on.
Questions about delete_application
Delete a deployed runtime application. It is categorised as a Destructive tool in the 20i MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for delete_application: 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 20i MCP Server. Nothing to install.
delete_application 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_application 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_application. 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_application is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue