Fetch logs from a pod — supports previous=true for crashed containers
AI agents call get_pod_logs to retrieve information from Kubernetes + Prometheus SRE 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 log data from Kubernetes pods without making any changes to cluster state or workloads. While logs may contain sensitive information (environment variables, secrets, request payloads, stack traces), the tool itself performs only a read operation.
From the tool's definition Tool name 'get_pod_logs' and description 'Fetch logs from a pod' indicate data retrieval with no modification or deletion. The mention of 'supports previous=true for crashed containers' confirms read-only log access.
Attacks that exploit this kind of access
Fetch logs from a pod — supports previous=true for crashed containers. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_pod_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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.
get_pod_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_pod_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_pod_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_pod_logs is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-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 →