start_service · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_service does on Coolify MCP Server

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

This tool triggers operational state changes on running services, which is an external operation execution. While not destructive (the service can be stopped), it is an Execute-class action because it initiates processes/services whose side effects depend on runtime context and arguments.

From the tool's definition Tool name 'start_service' combined with server description indicating ability to 'control applications, databases, and servers' and 'deploying services' demonstrates triggering of external operations.

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