delete_database_env

Delete an environment variable from a database.

SERVERCoolify SOURCEcoolify-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/delete-database-env.md

WHAT IT DOES

What delete_database_env does on Coolify

AI agents call delete_database_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.

RISK

Why delete_database_env is rated Critical

This tool permanently removes configuration from a database. Deletion of environment variables is irreversible—once deleted, the variable is gone unless manually re-added.

From the tool's definition Tool name is 'delete_database_env' and description states 'Delete an environment variable from a database.' The verb 'delete' combined with the irreversible nature of removing database environment variables (which often contain critical configuration or…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_database_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_database_env, this is the rule to start with:

delete_database_env Hidden

delete_database_env is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_database_env"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every delete_database_env call is checked against it from then on.

FAQ

Questions about delete_database_env

What does the delete_database_env tool do? +

Delete an environment variable from a database. 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.

How do I enforce a policy on delete_database_env? +

Register the Coolify MCP server in PolicyLayer and add a rule for delete_database_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.

What risk level is delete_database_env? +

delete_database_env is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_database_env? +

Yes. Add a rate_limit block to the delete_database_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.

How do I block delete_database_env completely? +

Set action: deny in the PolicyLayer policy for delete_database_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.

What MCP server provides delete_database_env? +

delete_database_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.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_database on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →