Read logs from all pods in a deployment
AI agents call k8s_deployment_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 Kubernetes pods with no side effects. It performs a query/fetch operation to surface existing logs for monitoring and debugging purposes, with no ability to create, modify, delete, or execute code. The blast radius of misuse is minimal — an attacker could exfiltrate logs containing sensitive information, but cannot alter the system state or trigger actions.
From the tool's definition Tool name contains 'logs' and description explicitly states 'Read logs from all pods in a deployment' — the verb 'Read' and the absence of any modification capability clearly indicate this is a read-only operation.
Attacks that exploit this kind of access
Read logs from all pods in a deployment. 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 k8s_deployment_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.
k8s_deployment_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 k8s_deployment_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 k8s_deployment_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.
k8s_deployment_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 →