Get a private key by UUID
AI agents call get_private_key to retrieve information from Coolify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a Read operation—it retrieves sensitive data (a private key) by identifier. However, the severity is elevated to 'high' rather than 'low' because private keys are cryptographic secrets whose exposure enables authentication and authorization bypass, account takeover, and lateral movement in the managed infrastructure.
From the tool's definition Tool name is 'get_private_key' with description 'Get a private key by UUID'. The verb 'Get' and absence of modification language clearly indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a private key by UUID. It is categorised as a Read tool in the Coolify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_private_key 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 get_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 get_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.
get_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 →