List requested number of tags for a particular image in docker hub
AI agents call docker_list_tags to retrieve information from MCP Docker Hub Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata (tags) from Docker Hub. It performs read-only retrieval of existing image tag information without creating, modifying, executing, or destroying any data. The operation is informational only, making it a Read category tool with low severity risk.
From the tool's definition Tool name is 'docker_list_tags' and description states it 'List requested number of tags for a particular image in docker hub' — a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
List requested number of tags for a particular image in docker hub. It is categorised as a Read tool in the MCP Docker Hub Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Docker Hub Server MCP server in PolicyLayer and add a rule for docker_list_tags: 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 MCP Docker Hub Server. Nothing to install.
docker_list_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the docker_list_tags 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_list_tags. 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_list_tags is provided by the MCP Docker Hub Server MCP server (sirsambhav221/mcpdcoker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →