push_image

Push a Docker image

SERVERDocker SOURCE@ckreiling/mcp-server-docker

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/docker/push-image.md

WHAT IT DOES

What push_image does on Docker

AI agents use push_image to create or update resources in Docker, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker environment.

RISK

Why push_image is rated Medium

Pushing an image to a registry is a write operation that creates or uploads data to a remote system. It is reversible (images can be deleted or overwritten in registries), so it is not Destructive. It does not execute arbitrary code on the host system and does not move money, making it Write rather than Execute or Financial.

From the tool's definition Tool named 'push_image' with description 'Push a Docker image' — the action uploads/writes a Docker image to a registry, modifying state in the remote registry.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs push_image safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For push_image, this is the rule to start with:

push_image Rate-limited

push_image stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_image": {
      "limits": [
        {
          "counter": "push_image_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every push_image call is checked against it from then on.

FAQ

Questions about push_image

What does the push_image tool do? +

Push a Docker image. It is categorised as a Write tool in the Docker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_image? +

Register the Docker MCP server in PolicyLayer and add a rule for push_image: 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 Docker. Nothing to install.

What risk level is push_image? +

push_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_image? +

Yes. Add a rate_limit block to the push_image 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.

How do I block push_image completely? +

Set action: deny in the PolicyLayer policy for push_image. 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.

What MCP server provides push_image? +

push_image is provided by the Docker MCP server (@ckreiling/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 19 Docker tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →