Check if the current user can perform an action
AI agents call auth-can-i 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 the Kubernetes RBAC system to determine if a user has permission to perform a specific action. It is purely informational—it reads authorization state and returns a yes/no answer with no side effects. While it could theoretically be used to enumerate permissions, it is a read-only query that cannot execute commands, modify resources, or cause destructive changes.
From the tool's definition Tool name 'auth-can-i' and description 'Check if the current user can perform an action' indicate a permission query operation that retrieves authorization status without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if the current user can perform an action. 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 auth-can-i: 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.
auth-can-i 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 auth-can-i 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 auth-can-i. 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.
auth-can-i 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 →