List Kubernetes configmaps in a namespace
AI agents call list-configmaps 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 is a read operation that queries and retrieves ConfigMap resources from a Kubernetes cluster. While it does not modify data, ConfigMaps often contain sensitive configuration including database credentials, API keys, or other secrets. The medium severity reflects that unauthorized read access to ConfigMaps could expose sensitive information, though the tool itself performs only harmless retrieval.
From the tool's definition Tool name 'list-configmaps' and description 'List Kubernetes configmaps in a namespace' indicate retrieval of existing configuration data with no modification or side effects.
Attacks that exploit this kind of access
List Kubernetes configmaps in a namespace. 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 list-configmaps: 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.
list-configmaps 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-configmaps 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-configmaps. 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-configmaps is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →