Retrieve logs from a Kubernetes pod or service with optional filtering for important messages.
AI agents call get_logs to retrieve information from K8s Observability MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves logs from Kubernetes pods or services with optional filtering. It performs no mutations, side effects, or irreversible actions. Logs are observability artifacts that already exist; querying them is a passive Read operation. The optional filtering is still read-focused and does not alter any underlying data.
From the tool's definition Tool name is 'get_logs' and description states 'Retrieve logs' — both indicate a read-only operation that queries existing observability data without modifying state.
Attacks that exploit this kind of access
Retrieve logs from a Kubernetes pod or service with optional filtering for important messages. It is categorised as a Read tool in the K8s Observability MCP MCP Server, which means it retrieves data without modifying state.
Register the K8s Observability 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 K8s Observability MCP. 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 K8s Observability MCP server (martinimarcello00/k8s-observability-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 →