start_application · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_application does on Coolify MCP Server

AI agents invoke start_application 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_application needs a policy

Starting an application is an Execute category action because it triggers external operations and state changes in the infrastructure managed by Coolify. While it is not destructive (the application can be stopped), it does execute a command/operation whose effects depend on arguments.

From the tool's definition The tool name is 'start_application' and description states it will 'Start an application'. This triggers an external operation (starting an application instance) whose effects depend on which application argument is provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_application Rate-limited

start_application 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_application": {
      "limits": [
        {
          "counter": "start_application_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_application

What does the start_application tool do? +

Start an application. 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_application? +

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

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

Can I rate-limit start_application? +

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

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

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

// THE FULL RECORD

start_application is one line of Coolify MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →