Read logs from Docker Compose services
AI agents call compose_logs to retrieve information from MCP Container Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves log data from running Docker Compose services. It performs query/fetch operations on existing logs without creating, modifying, deleting, or executing any actions. The read-only nature and lack of side effects make this a straightforward Read category risk with low severity.
From the tool's definition Tool name is 'compose_logs' and description explicitly states 'Read logs from Docker Compose services'. The verb 'read' and absence of any modification or execution capability clearly indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Read logs from Docker Compose services. It is categorised as a Read tool in the MCP Container Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Container Tools MCP server in PolicyLayer and add a rule for compose_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 MCP Container Tools. Nothing to install.
compose_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 compose_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 compose_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.
compose_logs is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). 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 →