List secrets in a namespace (values are not shown)
AI agents call k8s_list_secrets 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.
This tool performs a read operation (list/query) to retrieve Kubernetes secrets metadata from a namespace. Although it does not expose secret values, it reveals which secrets exist, their names, types, and metadata—information that could inform further attacks or reconnaissance.
From the tool's definition Tool name is 'k8s_list_secrets' with description stating 'List secrets in a namespace (values are not shown)'. The 'list' operation is a read-only query that retrieves data without modification.
Attacks that exploit this kind of access
List secrets in a namespace (values are not shown). 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_list_secrets: 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_list_secrets 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_list_secrets 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_list_secrets. 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_list_secrets 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 →