Delete an environment variable from an application
AI agents call delete_application_env to permanently remove resources in Coolify MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting environment variables is an irreversible operation that cannot be easily undone. Environment variables often control critical application behavior (API keys, database connections, feature flags, etc.). Removing them can break application functionality or expose security issues.
From the tool's definition Tool name contains 'delete' and description states 'Delete an environment variable from an application'. The verb 'delete' combined with removal of configuration data indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete an environment variable from an application. It is categorised as a Destructive tool in the Coolify MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP Server 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 MCP Server. 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 MCP server (kof70/coolify-mcp-server). 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 →