Low Risk

images

Lists Docker images with structured repository, tag, size, and creation info.

How to control images ↓

What images does on Make

AI agents call images to retrieve information from Make without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why images needs a policy

This tool performs a query operation to retrieve Docker image information (repository, tag, size, creation date). It has no side effects, does not execute code, modify data, or trigger external operations. It is purely informational and retrieves existing system state. Severity is low because unauthorized reading of Docker image metadata poses minimal direct risk to the system.

From the tool's definition Tool name 'images' combined with description 'Lists Docker images with structured repository, tag, size, and creation info' indicates a read-only operation that retrieves and queries Docker image metadata without modification or execution.

Documented attack patterns abuse exactly the kind of access images gives an agent:

How to control images

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for images:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "images": {}
  }
}

images is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about images

What does the images tool do? +

Lists Docker images with structured repository, tag, size, and creation info. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on images? +

Register the Make 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 Make. Nothing to install.

What risk level is images? +

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

Can I rate-limit images? +

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.

How do I block images completely? +

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.

What MCP server provides images? +

images is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.