AI agents call get_logs to retrieve information from Kube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Kubernetes log retrieval is a standard read-only operation that allows inspection of pod/container output without side effects. Even if logs contain sensitive information, the tool itself does not modify or delete resources.
From the tool's definition Tool name 'get_logs' indicates retrieval of log data from Kubernetes resources. The verb 'get' is a read operation that queries existing data without modification.
Attacks that exploit this kind of access
get_logs. It is categorised as a Read tool in the Kube MCP Server, which means it retrieves data without modifying state.
Register the Kube MCP server in PolicyLayer and add a rule for get_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 Kube. Nothing to install.
get_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 get_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 get_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.
get_logs is provided by the Kube MCP server (lochgeo/kube-mcp). 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 →