List allowed Docker images that can be used to create containers
AI agents call list_allowed_images to retrieve information from MCP Developer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays a list of pre-approved Docker images available for container creation. It performs only a read operation—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker gains only informational knowledge about available images, which may already be public or discoverable.
From the tool's definition Tool name 'list_allowed_images' and description 'List allowed Docker images' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List allowed Docker images that can be used to create containers. It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for list_allowed_images: 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 Developer Server. Nothing to install.
list_allowed_images 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 list_allowed_images 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 list_allowed_images. 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.
list_allowed_images is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). 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 →