Retrieve logs from a Docker container with optional filtering
AI agents call docker_container_logs to retrieve information from Docker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries container logs, which is fundamentally a read operation. However, container logs may contain sensitive information (credentials, API keys, personal data, system details), so while the action itself is read-only, the severity is elevated to medium due to potential information disclosure risks if an AI agent retrieves logs from containers it should not access.
From the tool's definition Tool name 'docker_container_logs' and description 'Retrieve logs from a Docker container' indicates a data retrieval operation with no modification or deletion capabilities.
Attacks that exploit this kind of access
Retrieve logs from a Docker container with optional filtering. It is categorised as a Read tool in the Docker MCP MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP server in PolicyLayer and add a rule for docker_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 MCP. Nothing to install.
docker_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 docker_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 docker_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.
docker_container_logs is provided by the Docker MCP server (sondt2709/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →