delete_application_env
Delete an environment variable from an application.
This record as markdown: /tools/coolify/delete-application-env.md
What delete_application_env does on Coolify
AI agents call delete_application_env to permanently remove resources in Coolify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_application_env is rated Critical
Deletion of environment variables is an irreversible operation that cannot be undone without recreation. Environment variables often contain critical configuration, secrets, or feature flags. Removing them can break application functionality, disable security controls, or expose the application to errors. This falls under Destructive rather than Write because the action cannot be reversed through normal operations.
From the tool's definition Tool name 'delete_application_env' explicitly uses 'delete', and description states 'Delete an environment variable from an application' — this irreversibly removes configuration data.
Attacks that exploit this kind of access
The rule that runs delete_application_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_application_env, this is the rule to start with:
delete_application_env 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 Coolify, apply this rule, and every delete_application_env call is checked against it from then on.
Questions about delete_application_env
Delete an environment variable from an application. It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP server in PolicyLayer and add a rule for delete_application_env: 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 Coolify. Nothing to install.
delete_application_env 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_env 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_env. 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_env is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coolify, and thousands of servers like it.
Across the catalogue