Get logs from a pod in a specified namespace
AI agents call get_pod_logs to retrieve information from Kubernetes Read Only MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves log data from Kubernetes pods. It performs a pure read operation with no capability to modify, execute code, delete resources, or move money. The read-only nature of the server and the absence of any state-changing operations confirms this classification.
From the tool's definition Tool is explicitly described as 'Get logs from a pod in a specified namespace' and the server is described as 'read-only interaction with Kubernetes clusters, allowing users to list resources and fetch logs without any create/update/delete operations.' The…
Documented attack patterns abuse exactly the kind of access get_pod_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kubernetes Read Only MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pod_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_pod_logs": {}
}
}get_pod_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get logs from a pod in a specified namespace. It is categorised as a Read tool in the Kubernetes Read Only MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes Read Only 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 Read Only 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 Read Only MCP Server MCP server (vijaykodam/kubernetes-readonly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kubernetes Read Only MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Kubernetes Read Only MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.