compose-logs
Retrieves Docker Compose service logs as structured entries.
This record as markdown: /tools/io-github-dave-london-build/compose-logs.md
What compose-logs does on Build
AI agents call compose-logs to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why compose-logs is rated Low
This tool simply retrieves and returns Docker Compose service logs as structured data. There are no side effects, no code execution, no data modification or deletion, and no financial operations. It is a pure read operation with minimal security risk - logs are typically non-sensitive operational data, and read access to logs is generally low-severity.
From the tool's definition The tool 'Retrieves Docker Compose service logs' performs a read-only operation. It fetches existing log data without modifying, creating, deleting, or executing any operations.
Attacks that exploit this kind of access
The rule that runs compose-logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compose-logs, this is the rule to start with:
compose-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 Build, apply this rule, and every compose-logs call is checked against it from then on.
Questions about compose-logs
Retrieves Docker Compose service logs as structured entries. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.
Register the Build 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 Build. 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 Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Build, and thousands of servers like it.
This server
Across the catalogue