start_service

Start a service.

SERVERCoolify SOURCEcoolify-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/start-service.md

WHAT IT DOES

What start_service does on Coolify

AI agents invoke start_service to trigger actions in Coolify. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why start_service is rated High

This tool executes an external action (starting a service) that can have cascading effects on running systems, deployments, or infrastructure. While not permanently destructive or financial, misuse (e.g., starting unintended critical services, causing resource exhaustion, or triggering dependent operations) poses significant operational risk.

From the tool's definition Tool name 'start_service' and description 'Start a service' indicate execution of a service start operation, which triggers external system behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

start_service Rate-limited

start_service stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_service": {
      "limits": [
        {
          "counter": "start_service_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about start_service

What does the start_service tool do? +

Start a service. It is categorised as a Execute tool in the Coolify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_service? +

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

start_service is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_service? +

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

Set action: deny in the PolicyLayer policy for start_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 start_service? +

start_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 → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →