List Kubernetes service accounts in a namespace
AI agents call list-serviceaccounts 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 query/listing operation (list) that retrieves service account information. It has no side effects—it does not create, modify, delete, execute code, or move money. Even though service account details could theoretically inform a later attack, the tool itself is purely informational.
From the tool's definition Tool name is 'list-serviceaccounts' and description states 'List Kubernetes service accounts in a namespace', which retrieves/enumerates existing data without modification.
Attacks that exploit this kind of access
List Kubernetes service accounts 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-serviceaccounts: 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-serviceaccounts 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-serviceaccounts 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-serviceaccounts. 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-serviceaccounts 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 →