create_docker_compose · MCP Software Engineer MCP

WHAT IT DOES

What create_docker_compose does on MCP Software Engineer

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

WHY IT NEEDS A POLICY

Why create_docker_compose needs a policy

This tool creates new Docker Compose configuration files, which is a reversible write operation. While it modifies the infrastructure-as-code, Docker Compose files are text-based configurations that can be edited or deleted without destructive consequences to running systems (assuming proper workflow).

From the tool's definition Tool name 'create_docker_compose' and description 'Create Docker Compose configuration for multi-container apps' indicate creation of configuration files that define containerized application infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_docker_compose Rate-limited

create_docker_compose 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_docker_compose": {
      "limits": [
        {
          "counter": "create_docker_compose_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 MCP Software Engineer, so you can run agents against it safely.

FAQ

Questions about create_docker_compose

What does the create_docker_compose tool do? +

Create Docker Compose configuration for multi-container apps. It is categorised as a Write tool in the MCP Software Engineer 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_docker_compose? +

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

What risk level is create_docker_compose? +

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

Can I rate-limit create_docker_compose? +

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

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

create_docker_compose is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.