This record as markdown: /tools/coolify/delete-private-key.md
What delete_private_key does on Coolify
AI agents call delete_private_key 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_private_key is rated Critical
This tool permanently removes a private key, which cannot be undone. Private keys are sensitive security credentials; their deletion causes irreversible loss of access and trust relationships. The blast radius is critical—a compromised agent could delete keys needed for authentication, encryption, or signing, causing service outages or security breaches.
From the tool's definition Tool name explicitly uses 'delete' and the description states it will 'Delete a private key by UUID', indicating irreversible removal of cryptographic credentials.
Attacks that exploit this kind of access
The rule that runs delete_private_key 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_private_key, this is the rule to start with:
delete_private_key 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_private_key call is checked against it from then on.
Questions about delete_private_key
Delete a private key by UUID. 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_private_key: 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_private_key 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_private_key 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_private_key. 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_private_key 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