Get secret metadata (values are base64 encoded)
AI agents call k8s_get_secret to retrieve information from Kubernetes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this is technically a Read operation (retrieves data without side effects), it accesses sensitive secret data that could include credentials, API keys, tokens, and other authentication material. The high severity reflects the sensitive nature of the data accessed, despite the lack of destructive capability. Misuse could lead to credential exposure and unauthorized system access.
From the tool's definition Tool name 'k8s_get_secret' and description 'Get secret metadata (values are base64 encoded)' indicate retrieval of secret data without modification. The tool retrieves and decodes base64-encoded secret values from Kubernetes.
Attacks that exploit this kind of access
Get secret metadata (values are base64 encoded). It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_get_secret: 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 MCP Server. Nothing to install.
k8s_get_secret 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 k8s_get_secret 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 k8s_get_secret. 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.
k8s_get_secret is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). 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 →