Remove environment variables from an application by key name.
AI agents call dokploy_delete_environment to permanently remove resources in Dokploy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting environment variables can break application functionality and cannot be easily undone, as the variables are permanently removed. This qualifies as Destructive rather than Write because it involves irreversible removal of configuration data. The high severity reflects that removing critical environment variables could cause immediate application failures in production environments.
From the tool's definition Tool name includes 'delete' and description states 'Remove environment variables from an application by key name' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Remove environment variables from an application by key name. It is categorised as a Destructive tool in the Dokploy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_delete_environment: 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. Nothing to install.
dokploy_delete_environment 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 dokploy_delete_environment 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 dokploy_delete_environment. 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.
dokploy_delete_environment is provided by the Dokploy MCP server (wyattjoh/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 →