list_kubernetes_pods
AI agents call list_kubernetes_pods to retrieve information from Google Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly indicates data retrieval with no side effects. Pod listing in Kubernetes is a standard read operation that queries cluster state without modification, deletion, or execution of code. No blast radius from misuse beyond information disclosure.
From the tool's definition Tool name 'list_kubernetes_pods' indicates a listing/query operation. Description is empty, but the tool name and sibling tools (list_gke_clusters, list_gke_node_pools, list_kubernetes_deployments, list_kubernetes_services) establish a clear pattern of…
Attacks that exploit this kind of access
list_kubernetes_pods. It is categorised as a Read tool in the Google Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for list_kubernetes_pods: 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 Google Cloud MCP Server. Nothing to install.
list_kubernetes_pods 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 list_kubernetes_pods 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 list_kubernetes_pods. 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.
list_kubernetes_pods is provided by the Google Cloud MCP Server MCP server (nsachin08/gcpmcp). 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 →