docker_tag_image

// WHEN AI AGENTS USE THIS TOOL

AI agents call docker_tag_image to retrieve information from Docker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON DOCKER_TAG_IMAGE

Even though docker_tag_image only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-alisaitteke-docker-mcp.yaml

tools:
  docker_tag_image:
    rules:
      - action: allow

See the full Docker policy for all 56 tools.

// DETAILS

Tool Name docker_tag_image

Category Read

MCP Server Docker MCP Server

Risk Level Low

// MORE DOCKER TOOLS

Destructive docker_compose_down Destructive docker_prune_containers Destructive docker_prune_images Destructive docker_prune_networks Destructive docker_prune_system Destructive docker_prune_volumes Destructive docker_remove_container Destructive docker_remove_image

View all 56 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like docker_tag_image have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the docker_tag_image tool do? +

Tag an image. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_tag_image? +

Add a rule in your Intercept YAML policy under the tools section for docker_tag_image. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docker MCP server.

What risk level is docker_tag_image? +

docker_tag_image is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit docker_tag_image? +

Yes. Add a rate_limit block to the docker_tag_image rule in your Intercept 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 docker_tag_image completely? +

Set action: deny in the Intercept policy for docker_tag_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 docker_tag_image? +

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

Enforce policies on Docker