Credentials this pod has access to (GCE MDS + projected SA + mounted files). Redacted.
AI agents call list_credentials 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 inventories credential metadata (service account tokens, projected credentials, mounted files) accessible to a pod—a read-only reconnaissance operation. While the blast radius is high (exposing credential locations enables further attacks), the tool itself performs no writes, execution, deletion, or financial operations.
From the tool's definition Tool name is 'list_credentials' and description states it retrieves 'Credentials this pod has access to (GCE MDS + projected SA + mounted files).
Attacks that exploit this kind of access
Credentials this pod has access to (GCE MDS + projected SA + mounted files). Redacted. 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_credentials: 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_credentials 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_credentials 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_credentials. 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_credentials 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 →