Get logs from a container.
AI agents call container_logs to retrieve information from Podman MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves container logs without modifying, deleting, or executing code. It is purely a query/inspection operation. While the server overall includes destructive tools (remove_container) and execute tools (exec_container, run_container), this specific tool only reads existing diagnostic output.
From the tool's definition Tool name 'container_logs' and description 'Get logs from a container' indicate a retrieval operation with no side effects. Logs are read-only diagnostic data.
Attacks that exploit this kind of access
Get logs from a container. It is categorised as a Read tool in the Podman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Podman MCP Server MCP server in PolicyLayer and add a rule for 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 Podman MCP Server. Nothing to install.
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 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 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.
container_logs is provided by the Podman MCP Server MCP server (kunwarmahen/podman-mcp-server). 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 →