Deletes an application in Dokploy.
AI agents call application-delete to permanently remove resources in Dokploy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an application from Dokploy. Deletion is an irreversible operation that cannot be undone through normal means, making it Destructive rather than Write. The high severity reflects the significant blast radius—loss of an entire application and potentially its associated data, configurations, and deployments. High confidence due to explicit 'delete' language in both name and description.
From the tool's definition Tool name is 'application-delete' and description states it 'Deletes an application in Dokploy.' The verb 'delete' and explicit mention of deletion indicate irreversible removal of data.
Attacks that exploit this kind of access
Deletes an application in Dokploy. It is categorised as a Destructive tool in the Dokploy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for application-delete: 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 Dokploy MCP Server. Nothing to install.
application-delete 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 application-delete 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 application-delete. 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.
application-delete is provided by the Dokploy MCP Server MCP server (limehawk/dokploy-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 →