enable_mcp
Enable the built-in Coolify MCP server endpoint at /mcp. Requires root-level token.
This record as markdown: /tools/coolify/enable-mcp.md
What enable_mcp does on Coolify
AI agents use enable_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.
Why enable_mcp is rated Medium
This tool enables a server endpoint, which is a configuration change (Write). However, it requires root-level access and activates an MCP server endpoint, which could expose significant attack surface if misused — enabling remote access/control capabilities.
From the tool's definition Enable the built-in Coolify MCP server endpoint at /mcp. Requires root-level token.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs enable_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 enable_mcp, this is the rule to start with:
enable_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every enable_mcp call is checked against it from then on.
Questions about enable_mcp
Enable 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.
Register the Coolify MCP server in PolicyLayer and add a rule for enable_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.
enable_mcp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_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.
Set action: deny in the PolicyLayer policy for enable_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.
enable_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.
More on Coolify, and thousands of servers like it.
This server
Across the catalogue