disable_mcp

Disable the built-in Coolify MCP server endpoint at /mcp. Requires root-level token.

SERVERCoolify SOURCEcoolify-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What disable_mcp does on Coolify

AI agents use disable_mcp 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.

RISK

Why disable_mcp is rated Medium

Disabling a service endpoint is a reversible configuration change (it can be re-enabled), placing it in the Write category. However, it carries high severity because disabling the MCP server endpoint could disrupt all MCP-dependent integrations and automation workflows, effectively cutting off API access for any connected agents or tools. Requires root-level token, indicating significant privilege requirement.

From the tool's definition Disable the built-in Coolify MCP server endpoint at /mcp

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

disable_mcp Rate-limited

disable_mcp 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": {
    "disable_mcp": {
      "limits": [
        {
          "counter": "disable_mcp_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about disable_mcp

What does the disable_mcp tool do? +

Disable the built-in Coolify MCP server endpoint at /mcp. Requires root-level token. 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 disable_mcp? +

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

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

Can I rate-limit disable_mcp? +

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

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

disable_mcp 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →