docker_compose
Run docker compose actions (up, down, ps, logs, restart).
This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-compose.md
What docker_compose does on Yaver
AI agents invoke docker_compose to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Action: up, down, ps, logs, restart |
directory | string | — | Directory with docker-compose.yml |
Parameters from the server's own tool schema.
Why docker_compose is rated High
docker_compose allows execution of arbitrary Docker Compose operations that start, stop, and manage containerized services. While some actions like 'ps' and 'logs' are read-only, the tool's primary capability encompasses 'up' and 'down' which actively control running infrastructure. An AI agent with misuse could start/stop critical services, modify network configurations, or trigger unintended deployments.
From the tool's definition Tool description explicitly states it 'Run[s] docker compose actions (up, down, ps, logs, restart)' — these are commands that execute and trigger external operations with side effects (container orchestration, service management).
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs docker_compose safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_compose, this is the rule to start with:
docker_compose 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docker_compose call is checked against it from then on.
Questions about docker_compose
Run docker compose actions (up, down, ps, logs, restart). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
docker_compose accepts 2 parameters: action, directory. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for 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 Yaver. Nothing to install.
docker_compose is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
docker_compose is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue