Delete a private key
AI agents call delete_private_key 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.
Private keys are sensitive cryptographic assets used for authentication, encryption, and authorization. Deletion is irreversible and cannot be undone. Loss of a private key can compromise infrastructure access, break deployments, and prevent recovery of encrypted data. This represents the most severe category (Destructive) due to the permanent nature of the action and the criticality of the affected resource.
From the tool's definition Tool name is 'delete_private_key' with description 'Delete a private key'. The verb 'Delete' combined with the object 'private key' indicates irreversible removal of cryptographic material.
Attacks that exploit this kind of access
Delete a private key. 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_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 MCP Server. 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 MCP server (pavelsukhachev/mcp-server-coolify). 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 →