List available Kubernetes contexts
AI agents call k8s_contexts to retrieve information from MCP Container Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate available Kubernetes contexts. It retrieves existing metadata about cluster configurations without creating, modifying, executing code, deleting resources, or affecting finances. The operation has minimal security impact as it only exposes cluster context names that would typically be discoverable through other means.
From the tool's definition Tool name 'k8s_contexts' and description 'List available Kubernetes contexts' indicate a query operation that retrieves configuration information without modification or side effects.
Attacks that exploit this kind of access
List available Kubernetes contexts. It is categorised as a Read tool in the MCP Container Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Container Tools MCP server in PolicyLayer and add a rule for k8s_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 MCP Container Tools. Nothing to install.
k8s_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_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_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_contexts is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). 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 →