disable_api

Disable the Coolify API. Requires root-level token.

SERVERCoolify SOURCEcoolify-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What disable_api does on Coolify

AI agents call disable_api to permanently remove resources in Coolify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why disable_api is rated Critical

Disabling the API is an irreversible operational action that would immediately cut off all API access to the Coolify platform, making it unavailable for all users and automated systems. This is effectively a service disruption action with a very high blast radius. It requires root-level token, indicating high privilege.

From the tool's definition Disable the Coolify API

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disable_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 disable_api, this is the rule to start with:

disable_api Hidden

disable_api is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "disable_api"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about disable_api

What does the disable_api tool do? +

Disable the Coolify API. Requires root-level token. It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on disable_api? +

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

disable_api is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit disable_api? +

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

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

disable_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 → Critical-risk tools on this server →

Across the catalogue

revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →