docker_images

List Docker images on the machine.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-images.md

WHAT IT DOES

What docker_images does on Yaver

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

RISK

Why docker_images is rated Low

The tool lists Docker images, which is a read-only operation that queries local system state. It has no side effects, does not execute code or containers, does not delete or modify images, and does not affect system functionality. The blast radius of misuse is minimal—an agent could only gain visibility into what Docker images are available locally.

From the tool's definition Tool name is 'docker_images' with description 'List Docker images on the machine.' This is a query operation that retrieves existing data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_images safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_images, this is the rule to start with:

docker_images Allowed

docker_images is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_images": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docker_images call is checked against it from then on.

FAQ

Questions about docker_images

What does the docker_images tool do? +

List Docker images on the machine. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_images? +

Register the Yaver MCP server in PolicyLayer and add a rule for docker_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 Yaver. Nothing to install.

What risk level is docker_images? +

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

Can I rate-limit docker_images? +

Yes. Add a rate_limit block to the docker_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 docker_images completely? +

Set action: deny in the PolicyLayer policy for docker_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 docker_images? +

docker_images is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

compare_images on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →