This record as markdown: /tools/deloc-mcp/delete-app.md
What delete_app does on Deloc
AI agents call delete_app to permanently remove resources in Deloc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_app is rated Critical
This tool irreversibly removes a published application and associated files, preventing recovery. An AI agent misusing it could permanently erase a user's deployed static site and its artifacts. While the blast radius is limited to a single app (not organizational data), the permanent nature and the published/live status of targets makes this a destructive action.
From the tool's definition Tool name is 'delete_app' and description explicitly states 'Permanently delete a published app and its files' — the word 'permanently' and 'delete' are unambiguous markers of irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs delete_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_app, this is the rule to start with:
delete_app 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 Deloc, apply this rule, and every delete_app call is checked against it from then on.
Questions about delete_app
Permanently delete a published app and its files. It is categorised as a Destructive tool in the Deloc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deloc 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 Deloc. 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 Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
Across the catalogue