This record as markdown: /tools/coolify/create-private-key.md
What create_private_key does on Coolify
AI agents use create_private_key to create or update resources in Coolify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.
Why create_private_key is rated Medium
Creating SSH private keys is a reversible Write operation (keys can be deleted or rotated), but rated high severity because misuse could generate credentials that compromise infrastructure security. An AI agent creating uncontrolled private keys could enable unauthorized access to systems.
From the tool's definition Tool named 'create_private_key' with description 'Create a new SSH private key.' – this creates and stores cryptographic material.
Attacks that exploit this kind of access
The rule that runs create_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 create_private_key, this is the rule to start with:
create_private_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every create_private_key call is checked against it from then on.
Questions about create_private_key
Create a new SSH private key. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify 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. 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 (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.
This server
Across the catalogue