images
Lists Docker images with structured repository, tag, size, and creation info.
This record as markdown: /tools/io-github-dave-london-lint/images.md
What images does on Lint
AI agents call images to retrieve information from Lint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why images is rated Low
This tool performs read-only operations to query and retrieve information about Docker images. It does not create, modify, delete, execute commands, or involve financial transactions. The blast radius is minimal since it only exposes metadata about images already present on the system.
From the tool's definition Tool name is 'images' and description states 'Lists Docker images with structured repository, tag, size, and creation info.' The verb 'Lists' and the focus on retrieving and querying existing Docker image metadata with no modification capability.
Attacks that exploit this kind of access
The rule that runs images safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For images, this is the rule to start with:
images is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lint, apply this rule, and every images call is checked against it from then on.
Questions about images
Lists Docker images with structured repository, tag, size, and creation info. It is categorised as a Read tool in the Lint MCP Server, which means it retrieves data without modifying state.
Register the Lint MCP server in PolicyLayer and add a rule for 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 Lint. Nothing to install.
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 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 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.
images is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lint, and thousands of servers like it.
This server
Across the catalogue