Pods in this pod
AI agents call list_namespace_pods_tool to retrieve information from Gke Cred Audit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about pods within a namespace. It has no capability to modify, delete, execute commands, or trigger side effects. The blast radius of a misuse is limited to information disclosure about pod inventory within the cluster. While this information could inform further attacks, the tool itself only reads and lists existing resources.
From the tool's definition Tool name 'list_namespace_pods_tool' and context 'Pods in this pod' indicates retrieval/listing of pod resources with no modification capability.
Attacks that exploit this kind of access
Pods in this pod. It is categorised as a Read tool in the Gke Cred Audit MCP Server, which means it retrieves data without modifying state.
Register the Gke Cred Audit MCP server in PolicyLayer and add a rule for list_namespace_pods_tool: 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 Gke Cred Audit. Nothing to install.
list_namespace_pods_tool 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_namespace_pods_tool 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_namespace_pods_tool. 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_namespace_pods_tool is provided by the Gke Cred Audit MCP server (rrupesh/mcp-test). 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 →