This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-build.md
What docker_build does on Yaver
AI agents invoke docker_build 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 |
|---|---|---|---|
tag | string | — | Image tag |
directory | string | — | |
dockerfile | string | — |
Parameters from the server's own tool schema.
Why docker_build is rated High
This tool triggers external operations (Docker build process) whose effects depend on the Dockerfile contents provided as arguments. While not immediately destructive to existing data, it executes untrusted code during the build process and can have significant side effects (resource consumption, network access, creation of container artifacts).
From the tool's definition Tool name is 'docker_build' and description states 'Build a Docker image from Dockerfile.' Building a Docker image executes arbitrary code defined in the Dockerfile, including RUN commands that can execute shell commands, install packages, and modify the…
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs docker_build 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_build, this is the rule to start with:
docker_build 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_build call is checked against it from then on.
Questions about docker_build
Build a Docker image from Dockerfile. 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_build accepts 3 parameters: tag, directory, dockerfile. 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_build: 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_build 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_build 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_build. 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_build 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