generate_docker_compose · Docker Explorer MCP: Risk & Policy

WHAT IT DOES

What generate_docker_compose does on Docker Explorer

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

WHY IT NEEDS A POLICY

Why generate_docker_compose needs a policy

This tool generates Docker Compose files, which are configuration artifacts that define multi-container application layouts. Generation is a Write operation—it creates new configuration data. Severity is high because a malicious or erroneous Docker Compose file could orchestrate containers with privilege escalation, volume mounts to sensitive paths, or network exposure.

From the tool's definition Tool name 'generate_docker_compose' indicates creation of Docker Compose configuration files. Related sibling tools include 'generate_dockerfile', which parallels the generative/creation pattern.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_docker_compose Rate-limited

generate_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": {
    "generate_docker_compose": {
      "limits": [
        {
          "counter": "generate_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 Docker Explorer, so you can run agents against it safely.

FAQ

Questions about generate_docker_compose

What does the generate_docker_compose tool do? +

generate_docker_compose. It is categorised as a Write tool in the Docker Explorer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_docker_compose? +

Register the Docker Explorer MCP server in PolicyLayer and add a rule for generate_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 Docker Explorer. Nothing to install.

What risk level is generate_docker_compose? +

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

Can I rate-limit generate_docker_compose? +

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

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

generate_docker_compose is provided by the Docker Explorer MCP server (jar285/mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.