update_service

Update a service by UUID.

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-service.md

WHAT IT DOES

What update_service does on Coolify

AI agents use update_service 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_service is rated Medium

The tool modifies service configuration/state by ID. While not irreversible (no delete/drop), updating a service can cause deployment changes, restart cascades, or configuration conflicts with potentially significant blast radius. Categorized as Write (reversible modification) rather than Execute, as it targets a specific service resource rather than executing arbitrary code.

From the tool's definition Tool name 'update_service' and description 'Update a service by UUID' indicate modification of existing service configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_service Rate-limited

update_service 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_service": {
      "limits": [
        {
          "counter": "update_service_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_service call is checked against it from then on.

FAQ

Questions about update_service

What does the update_service tool do? +

Update a service by UUID. 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_service? +

Register the Coolify MCP server in PolicyLayer and add a rule for update_service: 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_service? +

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

Can I rate-limit update_service? +

Yes. Add a rate_limit block to the update_service 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_service completely? +

Set action: deny in the PolicyLayer policy for update_service. 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_service? +

update_service 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 →