api_control · Coolify MCP: Risk & Policy

WHAT IT DOES

What api_control does on Coolify

AI agents use api_control to create or update resources in Coolify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.

WHY IT NEEDS A POLICY

Why api_control needs a policy

This tool modifies infrastructure configuration by toggling API access, which is a Write-category action (reversible state change). Severity is high because disabling the API could disrupt all dependent services and integrations, making it a significant operational impact, though not as severe as destructive deletion or financial transactions.

From the tool's definition The tool description states it can 'Enable or disable the Coolify API' and 'Requires write permission.' These are reversible configuration changes that modify system state without deleting data or executing arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

api_control Rate-limited

api_control stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "api_control": {
      "limits": [
        {
          "counter": "api_control_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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, so you can run agents against it safely.

FAQ

Questions about api_control

What does the api_control tool do? +

Enable or disable the Coolify API. Requires write permission. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on api_control? +

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

api_control is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit api_control? +

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

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

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