update_private_key

Update an existing private key.

SERVERCoolify SOURCEcoolify-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/update-private-key.md

WHAT IT DOES

What update_private_key does on Coolify

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

RISK

Why update_private_key is rated Medium

This tool modifies an existing private key, which is a reversible write operation. However, the severity is high because private keys are critical security assets—unauthorized modification could compromise authentication, encryption, and access controls across deployed applications.

From the tool's definition Tool name 'update_private_key' and description 'Update an existing private key' indicate modification of security credentials.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_private_key, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every update_private_key call is checked against it from then on.

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, 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 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. 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 (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →