Create a new SSH private key
AI agents use create_private_key to create or update resources in Coolify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify MCP Server environment.
This tool creates and stores a new SSH private key, which is a reversible Write operation. However, the severity is elevated to 'high' because SSH private keys are security-critical credentials. Misuse could result in unauthorized access being provisioned, though the key creation itself is not destructive or irreversible—keys can be regenerated or revoked.
From the tool's definition Tool name is 'create_private_key' and description states 'Create a new SSH private key'. This creates cryptographic credentials that are stored and used for authentication/access control.
Attacks that exploit this kind of access
Create a new SSH private key. It is categorised as a Write tool in the Coolify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_private_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_private_key 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 →