This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-exec.md
What docker_exec does on Yaver
AI agents invoke docker_exec 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 |
|---|---|---|---|
command | string | Yes | Command to execute |
container | string | Yes | Container name or ID |
Parameters from the server's own tool schema.
Why docker_exec is rated High
This tool runs code/commands with side effects dependent on arguments. Docker container execution can modify container state, access container filesystems, spawn processes, or interact with networked services.
From the tool's definition Tool name 'docker_exec' and description 'Execute a command inside a Docker container' explicitly indicate arbitrary command execution within a containerized environment.
Attacks that exploit this kind of access
The rule that runs docker_exec 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_exec, this is the rule to start with:
docker_exec 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_exec call is checked against it from then on.
Questions about docker_exec
Execute a command inside a Docker container. 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_exec accepts 2 parameters: command, container. Required: command, container. 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_exec: 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_exec 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_exec 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_exec. 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_exec 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