列出Helm Releases
AI agents call helm_list 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 state of Helm releases in a Kubernetes cluster. It performs a read-only operation that has no side effects—it neither creates, modifies, deletes, nor executes code. The function is purely informational, returning a list of deployed releases for inspection purposes. No blast radius for accidental misuse.
From the tool's definition Tool name 'helm_list' and description '列出Helm Releases' (List Helm Releases) indicate it retrieves and displays existing Helm release information without modifying or deleting resources.
Attacks that exploit this kind of access
列出Helm Releases. 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 helm_list: 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.
helm_list 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 helm_list 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 helm_list. 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.
helm_list is provided by the Kubernetes MCP Server MCP server (secret-deus/kubernetes-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 →