create_dockercompose_application · Coolify MCP Tools MCP

WHAT IT DOES

What create_dockercompose_application does on Coolify MCP Tools

AI agents use create_dockercompose_application to create or update resources in Coolify MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify MCP Tools environment.

WHY IT NEEDS A POLICY

Why create_dockercompose_application needs a policy

This tool creates a new application by defining it via Docker Compose, which is a reversible operation (the application can be deleted or reconfigured). It modifies the Coolify infrastructure state by adding a new managed application, but does not execute arbitrary code, delete existing resources, or move money. The 'create' action is characteristic of Write category.

From the tool's definition Tool name is 'create_dockercompose_application' and description states 'Create application from Docker Compose'. The verb 'create' indicates creation of new infrastructure/application configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dockercompose_application Rate-limited

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

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 create_dockercompose_application

What does the create_dockercompose_application tool do? +

Create application from Docker Compose. It is categorised as a Write tool in the Coolify MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dockercompose_application? +

Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for create_dockercompose_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 create_dockercompose_application? +

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

Can I rate-limit create_dockercompose_application? +

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

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

create_dockercompose_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.