This record as markdown: /tools/coolify/list-private-keys.md
What list_private_keys does on Coolify
AI agents call list_private_keys to retrieve information from Coolify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_private_keys is rated Low
This tool retrieves sensitive SSH private keys without modifying them. While the severity is high due to the sensitive nature of the data exposed (private keys enable authentication and access), the operation itself is Read-only.
From the tool's definition Tool name 'list_private_keys' and description 'List all SSH private keys' indicate a retrieval operation. The verb 'list' is a classic Read operation (query/fetch pattern).
Attacks that exploit this kind of access
The rule that runs list_private_keys 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 list_private_keys, this is the rule to start with:
list_private_keys is read-only, so it stays allowed. 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 list_private_keys call is checked against it from then on.
Questions about list_private_keys
List all SSH private keys. It is categorised as a Read tool in the Coolify MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP server in PolicyLayer and add a rule for list_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.
list_private_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_private_keys 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