Manage SSH keys: list/get/create/update/delete
AI agents call private_keys 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.
While the tool spans multiple categories (Read via list/get, Write via create/update, Destructive via delete), the presence of 'delete' for SSH keys—which are sensitive cryptographic credentials essential for infrastructure access—makes this Destructive. Deletion of SSH keys cannot be reversed and can immediately revoke authentication access to critical systems.
From the tool's definition Tool description explicitly states 'delete' capability for SSH keys. The tool manages SSH keys with create/update/delete operations, where delete operations on cryptographic credentials are irreversible and cannot be undone.
Attacks that exploit this kind of access
Manage SSH keys: list/get/create/update/delete. 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 private_keys: 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.
private_keys 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 private_keys 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 private_keys. 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.
private_keys is provided by the Coolify MCP server (jurislm/coolify-mcp). 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 →