Generate a docker-compose.yml file for multi-service applications
AI agents use create_docker_compose to create or update resources in MCP Developer Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Developer Server environment.
This tool creates a new docker-compose.yml configuration file, which is a reversible write operation. While docker-compose files can orchestrate containers and services, the tool only generates the configuration file itself—it does not execute, deploy, or launch containers.
From the tool's definition Tool description states it will 'Generate a docker-compose.yml file' — a create/write operation that produces a configuration file.
Attacks that exploit this kind of access
Generate a docker-compose.yml file for multi-service applications. It is categorised as a Write tool in the MCP Developer Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Developer Server 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 Developer Server. Nothing to install.
create_docker_compose is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_docker_compose is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →