deploy_application · Coolify MCP Tools MCP: Risk & Policy

WHAT IT DOES

What deploy_application does on Coolify MCP Tools

AI agents invoke deploy_application to trigger actions in Coolify MCP Tools. 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_application needs a policy

Deployment is an Execute action—it runs external operations that trigger builds, container orchestration, service restarts, and infrastructure changes. While reversible via redeployment, the effects are substantial and depend entirely on what application and configuration are targeted.

From the tool's definition Tool name 'deploy_application' and description 'Deploy an application' indicate triggering an external operation (deployment) whose effects depend on arguments (which application, deployment configuration, environment).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_application Rate-limited

deploy_application 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_application": {
      "limits": [
        {
          "counter": "deploy_application_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 Tools, so you can run agents against it safely.

FAQ

Questions about deploy_application

What does the deploy_application tool do? +

Deploy an application. It is categorised as a Execute tool in the Coolify MCP Tools 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_application? +

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

What risk level is deploy_application? +

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

Can I rate-limit deploy_application? +

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

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

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