fetch_container_logs
Fetch logs for a Docker container
This record as markdown: /tools/docker/fetch-container-logs.md
What fetch_container_logs does on Docker
AI agents call fetch_container_logs to retrieve information from Docker without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fetch_container_logs is rated Low
This tool retrieves container logs, which is a read-only query operation with no side effects. The logs are already generated and the tool merely accesses them. Severity is low because log access has minimal blast radius unless logs contain sensitive credentials (which would be a data exposure issue, not an inherent property of the tool itself).
From the tool's definition Tool name 'fetch_container_logs' and description 'Fetch logs for a Docker container' indicate retrieval of existing log data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs fetch_container_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_container_logs, this is the rule to start with:
fetch_container_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 Docker, apply this rule, and every fetch_container_logs call is checked against it from then on.
Questions about fetch_container_logs
Fetch logs for a Docker container. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP server in PolicyLayer and add a rule for fetch_container_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 Docker. Nothing to install.
fetch_container_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 fetch_container_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 fetch_container_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.
fetch_container_logs is provided by the Docker MCP server (@ckreiling/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue