fetch_container_logs
Retrieve container output
Part of the Docker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call fetch_container_logs to retrieve information from Docker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON FETCH_CONTAINER_LOGS
Even though fetch_container_logs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
fetch_container_logs:
rules:
- action: allowSee the full Docker policy for all 19 tools.
DETAILS
MORE DOCKER TOOLS
list_containers Read list_images Read list_networks Read list_volumes Read create_container Write create_network Write create_volume Write push_image Write SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the fetch_container_logs tool do?
Retrieve container output. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on fetch_container_logs?
Add a rule in your Intercept YAML policy under the tools section for fetch_container_logs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docker MCP server.
What risk level is fetch_container_logs?
fetch_container_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit fetch_container_logs?
Yes. Add a rate_limit block to the fetch_container_logs rule in your Intercept 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.
How do I block fetch_container_logs completely?
Set action: deny in the Intercept 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.
What MCP server provides fetch_container_logs?
fetch_container_logs is provided by the Docker MCP server (ckreiling/mcp-server-docker). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON DOCKER
Open source. One binary. Zero dependencies.