update_private_key · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_private_key does on Coolify MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_private_key needs a policy

This tool modifies (rather than deletes or creates) an existing private key, which is a sensitive credential. Unauthorized updates to private keys could compromise infrastructure security and enable unauthorized access.

From the tool's definition Tool name 'update_private_key' and description 'Update an existing private key' indicate modification of cryptographic credentials used for infrastructure authentication.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_private_key Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_private_key": {
      "limits": [
        {
          "counter": "update_private_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Coolify MCP Server, so you can run agents against it safely.

FAQ

Questions about update_private_key

What does the update_private_key tool do? +

Update an existing 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.

How do I enforce a policy on update_private_key? +

Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_private_key? +

update_private_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_private_key? +

Yes. Add a rate_limit block to the update_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.

How do I block update_private_key completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_private_key? +

update_private_key is provided by the Coolify MCP Server MCP server (pavelsukhachev/mcp-server-coolify). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.