This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-logs.md
What docker_logs does on Yaver
AI agents call docker_logs 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 |
|---|---|---|---|
tail | integer | — | Number of lines (default: 100) |
container | string | Yes | Container name or ID |
Parameters from the server's own tool schema.
Why docker_logs is rated Low
This tool only accesses and returns log data from an already-running Docker container. It has no side effects—it does not create, modify, delete, or execute anything. The blast radius of misuse is minimal: an attacker could potentially read sensitive information in logs, but cannot affect the container or system state. This is a straightforward Read category tool with low severity.
From the tool's definition docker_logs retrieves container logs without modifying, deleting, or executing operations. The description states 'Get logs from a Docker container,' which is a read-only query operation.
Attacks that exploit this kind of access
The rule that runs docker_logs 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_logs, this is the rule to start with:
docker_logs 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_logs call is checked against it from then on.
Questions about docker_logs
Get logs from a Docker container. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
docker_logs accepts 2 parameters: tail, container. Required: container. 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_logs: 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_logs 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_logs 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_logs. 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_logs 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