Deletes an existing domain configuration in Dokploy by its ID.
AI agents call domain-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 domain configurations, which cannot be undone and will directly impact application accessibility and routing. While not as critical as application deletion, domain deletion causes service disruption and represents a destructive action.
From the tool's definition Tool name 'domain-delete' and description 'Deletes an existing domain configuration in Dokploy by its ID' explicitly indicate irreversible deletion of domain configuration data.
Attacks that exploit this kind of access
Deletes an existing domain configuration in Dokploy by its ID. 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 domain-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.
domain-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 domain-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 domain-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.
domain-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 →