List Kubernetes resource quotas in a namespace
AI agents call list-resourcequotas 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 queries and displays existing Kubernetes resource quota configurations without making any changes to cluster state. Listing operations are read-only with no side effects, fitting the Read category. Severity is low because viewing resource quotas poses minimal security risk—it only exposes quota metadata which is typically non-sensitive operational information.
From the tool's definition Tool name 'list-resourcequotas' and description 'List Kubernetes resource quotas in a namespace' indicate a retrieval operation with no modification or deletion of resources.
Attacks that exploit this kind of access
List Kubernetes resource quotas 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-resourcequotas: 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-resourcequotas 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-resourcequotas 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-resourcequotas. 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-resourcequotas 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 →