This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-history.md
What docker_history does on Yaver
AI agents call docker_history 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
image | string | Yes |
Parameters from the server's own tool schema.
Why docker_history is rated Low
docker_history queries and displays Docker image layer history, which is a read-only operation that retrieves information about image composition without side effects. It does not execute code, modify images, delete data, or commit financial transactions.
From the tool's definition Tool description 'Show image layer history' indicates retrieval of existing Docker image metadata with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs docker_history 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_history, this is the rule to start with:
docker_history 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 Yaver, apply this rule, and every docker_history call is checked against it from then on.
Questions about docker_history
Show image layer history. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
docker_history accepts 1 parameter: image. Required: image. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for docker_history: 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.
docker_history 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_history 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_history. 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_history 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue