This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-push.md
What docker_push does on Yaver
AI agents invoke docker_push 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_push is rated High
Pushing a Docker image to a registry is an external operation that modifies state on a remote system. It is not purely destructive (the image still exists locally), but it is not a simple write either — it executes an external publish operation with potentially broad blast radius (e.g., overwriting a public or shared image tag, exposing sensitive code/data).
From the tool's definition 'Push a Docker image to registry' — this triggers an external operation (pushing to a remote registry) whose effects depend on the image and registry arguments.
Attacks that exploit this kind of access
The rule that runs docker_push 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_push, this is the rule to start with:
docker_push 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_push call is checked against it from then on.
Questions about docker_push
Push a Docker image to registry. 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_push 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_push: 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_push 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_push 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_push. 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_push 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