This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-pull.md
What docker_pull does on Yaver
AI agents invoke docker_pull 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 |
|---|---|---|---|
image | string | Yes |
Parameters from the server's own tool schema.
Why docker_pull is rated High
Pulling a Docker image triggers an external network operation that downloads potentially large amounts of data from a registry and modifies the local Docker image cache. This is not a simple read (it has side effects on the local system) and not purely destructive. It falls under Execute as it runs an external operation whose effects depend on the image argument supplied.
From the tool's definition Pull a Docker image
Attacks that exploit this kind of access
The rule that runs docker_pull 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_pull, this is the rule to start with:
docker_pull 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_pull call is checked against it from then on.
Questions about docker_pull
Pull a Docker image. 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_pull accepts 1 parameter: image. Required: image. 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_pull: 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_pull 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_pull 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_pull. 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_pull 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