enable_api

Enable the Coolify API. Requires root-level token.

SERVERCoolify SOURCEcoolify-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/enable-api.md

WHAT IT DOES

What enable_api does on Coolify

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

RISK

Why enable_api is rated High

Enabling an API is an operational action that changes system state (from disabled to enabled), making the API surface accessible. This is not a simple data read or write — it triggers a systemic change that affects what operations are accessible externally. It requires root-level token, indicating high privilege. Misuse could expose the entire Coolify API to external access, hence high severity.

From the tool's definition 'Enable the Coolify API' - this triggers an external operational state change on the Coolify system

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs enable_api safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_api, this is the rule to start with:

enable_api Rate-limited

enable_api 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": {
    "enable_api": {
      "limits": [
        {
          "counter": "enable_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every enable_api call is checked against it from then on.

FAQ

Questions about enable_api

What does the enable_api tool do? +

Enable the Coolify API. Requires root-level token. 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 enable_api? +

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

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

Can I rate-limit enable_api? +

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

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

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

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →