List all available kubectl contexts
AI agents call k8s_get_contexts 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 retrieves metadata about available Kubernetes contexts through a list operation. It has no side effects, performs no modifications, executes no commands, and poses minimal risk. The only potential concern is information disclosure (listing available contexts), but this is low severity as context names alone do not expose sensitive data without further actions.
From the tool's definition Tool name is 'k8s_get_contexts' and description states 'List all available kubectl contexts' — a pure query operation that retrieves configuration information without modifying or executing any cluster actions.
Attacks that exploit this kind of access
List all available kubectl contexts. 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_get_contexts: 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_get_contexts 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_get_contexts 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_get_contexts. 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_get_contexts 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 →