coolify.deploy_template · Coolify MCP Server MCP

WHAT IT DOES

What coolify.deploy_template does on Coolify MCP Server

AI agents invoke coolify.deploy_template to trigger actions in Coolify MCP Server. 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.

WHY IT NEEDS A POLICY

Why coolify.deploy_template needs a policy

Deploying an application is an Execute action—it runs a deployment process that provisions infrastructure, starts services, and makes the application live. While predefined templates mitigate some risk (versus arbitrary code execution), deployment still triggers external operations whose effects depend on template selection and configuration.

From the tool's definition Tool name 'deploy_template' and description 'Deploy an application from a predefined template' indicate execution of a deployment operation that triggers external infrastructure changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

coolify.deploy_template Rate-limited

coolify.deploy_template 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": {
    "coolify.deploy_template": {
      "limits": [
        {
          "counter": "coolify.deploy_template_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about coolify.deploy_template

What does the coolify.deploy_template tool do? +

Deploy an application from a predefined template. It is categorised as a Execute tool in the Coolify MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on coolify.deploy_template? +

Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for coolify.deploy_template: 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 MCP Server. Nothing to install.

What risk level is coolify.deploy_template? +

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

Can I rate-limit coolify.deploy_template? +

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

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

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