start_service · Coolify MCP Tools MCP: Risk & Policy

WHAT IT DOES

What start_service does on Coolify MCP Tools

AI agents invoke start_service to trigger actions in Coolify MCP Tools. 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.

WHY IT NEEDS A POLICY

Why start_service needs a policy

Starting a service is an Execute action—it triggers an external operation that changes system state and whose blast radius depends on the service being started. It is not Read (no data retrieval), not Write (not creating/modifying data reversibly—it changes running state), not Destructive (starting is reversible via stop), and not Financial.

From the tool's definition Tool is named 'start_service' with description 'Start a service'. This triggers an external operation (service startup) whose effects depend on which service is targeted and its configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

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