Medium Risk

pull_image

Download a Docker image from a registry

Risk signalsDownloads external images to host

Part of the Docker server.

pull_image can modify Docker data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DOCKER →

Free to start. No card required.

AI agents use pull_image to create or modify resources in Docker. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call pull_image repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Docker.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pull_image": {
      "limits": [
        {
          "counter": "pull_image_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Docker policy for all 19 tools.

Get this rule live on your own Docker server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOCKER →

View all 19 tools →

These attack patterns abuse exactly the kind of access pull_image gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so pull_image only ever does what you allow.

SECURE DOCKER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the pull_image tool do? +

Download a Docker image from a registry. 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 pull_image? +

Register the Docker MCP server in PolicyLayer and add a rule for pull_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 pull_image? +

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

Can I rate-limit pull_image? +

Yes. Add a rate_limit block to the pull_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 pull_image completely? +

Set action: deny in the PolicyLayer policy for pull_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 pull_image? +

pull_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.

Enforce policy on every Docker tool call.

Deterministic rules across all 19 Docker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.