AI agents call list_kube_contexts to retrieve information from Kube Lint without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays available Kubernetes contexts without modifying any infrastructure, executing commands, or causing side effects. It is purely informational, analogous to 'kubectl config get-contexts'. The blast radius of misuse is minimal—an attacker gains knowledge of available clusters but cannot interact with them without additional tools.
From the tool's definition Tool name 'list_kube_contexts' and description 'List available kubectl contexts' indicate a query/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
List available kubectl contexts.\n. It is categorised as a Read tool in the Kube Lint MCP Server, which means it retrieves data without modifying state.
Register the Kube Lint MCP server in PolicyLayer and add a rule for list_kube_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 Kube Lint. Nothing to install.
list_kube_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 list_kube_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 list_kube_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.
list_kube_contexts is provided by the Kube Lint MCP server (sophotechlabs/kube-lint-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 →