This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-inspect.md
What docker_inspect does on Yaver
AI agents call docker_inspect 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 |
|---|---|---|---|
target | string | Yes | Container or image name/ID |
Parameters from the server's own tool schema.
Why docker_inspect is rated Low
The inspect operation is a diagnostic query that reads metadata and status from existing Docker containers or images. It returns information in JSON format but does not create, modify, delete, or execute code. The blast radius is minimal since it only exposes existing configuration and runtime information accessible to the user running the command, posing no destructive or execution risk.
From the tool's definition Tool name 'docker_inspect' and description 'Inspect a Docker container or image (detailed JSON)' indicate a query operation that retrieves and returns detailed information about Docker resources without modifying them.
Attacks that exploit this kind of access
The rule that runs docker_inspect 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_inspect, this is the rule to start with:
docker_inspect 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_inspect call is checked against it from then on.
Questions about docker_inspect
Inspect a Docker container or image (detailed JSON). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
docker_inspect accepts 1 parameter: target. Required: target. 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_inspect: 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_inspect 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_inspect 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_inspect. 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_inspect 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