deploy_webhook · Coolify MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_webhook does on Coolify MCP Server

AI agents invoke deploy_webhook 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 deploy_webhook needs a policy

This tool executes an external operation (deployment pipeline activation) rather than simply reading or writing data. Deployments can modify production systems, restart services, and affect live applications. While not inherently destructive or financial, deployment triggering is an Execute-class operation due to its ability to change system state in ways that depend on the arguments and context.

From the tool's definition Tool triggers deployment via webhook. 'Trigger deployment' indicates execution of a build/deployment pipeline whose effects depend on what is being deployed and the target environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_webhook Rate-limited

deploy_webhook 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": {
    "deploy_webhook": {
      "limits": [
        {
          "counter": "deploy_webhook_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 deploy_webhook

What does the deploy_webhook tool do? +

Trigger deployment via webhook. 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 deploy_webhook? +

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

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

Can I rate-limit deploy_webhook? +

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

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

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