Posture for a specific pod by name in this pod
AI agents call describe_pod 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 retrieves pod metadata and posture information. While it provides visibility into potentially sensitive pod configuration (which could include credentials or RBAC details in logs/descriptions), it only reads data and has no side effects. It is classified as Read.
From the tool's definition Tool name is 'describe_pod' and description states it retrieves 'Posture for a specific pod by name' — a querying/inspection operation with no modification or destructive capability.
Attacks that exploit this kind of access
Posture for a specific pod by name 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 describe_pod: 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.
describe_pod 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 describe_pod 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 describe_pod. 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.
describe_pod 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 →