stop_service

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke stop_service to trigger processes or run actions in Coolify. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON STOP_SERVICE

stop_service can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

coolify.yaml

tools:
  stop_service:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Coolify policy for all 26 tools.

// DETAILS

Tool Name stop_service

Category Execute

MCP Server Coolify MCP Server

Risk Level High

// MORE COOLIFY TOOLS

Execute execute_command_application Execute restart_application Execute restart_service Execute start_application Execute start_service Execute stop_application Write create_application Write create_private_key

View all 26 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like stop_service have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

stop_service is one of the high-risk operations in Coolify. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the stop_service tool do? +

Stop 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 stop_service? +

Add a rule in your Intercept YAML policy under the tools section for stop_service. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Coolify MCP server.

What risk level is stop_service? +

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

Can I rate-limit stop_service? +

Yes. Add a rate_limit block to the stop_service rule in your Intercept 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 stop_service completely? +

Set action: deny in the Intercept policy for stop_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 stop_service? +

stop_service is provided by the Coolify MCP server (coolify-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Coolify