helm_install · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What helm_install does on Kubernetes MCP Server

AI agents invoke helm_install to trigger actions in Kubernetes MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why helm_install needs a policy

Installing a Helm chart is an Execute-level operation: it deploys workloads, creates Kubernetes resources (Deployments, Services, ConfigMaps, etc.), and runs containers in the cluster. While it creates resources (Write), the act of deploying and running arbitrary workloads from a chart represents execution of external operations with broad blast radius.

From the tool's definition 安装Helm Chart (Install Helm Chart) - deploys and executes a Helm chart into a Kubernetes cluster, triggering creation of resources, running containers, and configuring cluster state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

helm_install Rate-limited

helm_install stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "helm_install": {
      "limits": [
        {
          "counter": "helm_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kubernetes MCP Server, so you can run agents against it safely.

FAQ

Questions about helm_install

What does the helm_install tool do? +

安装Helm Chart. It is categorised as a Execute tool in the Kubernetes MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on helm_install? +

Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for helm_install: 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.

What risk level is helm_install? +

helm_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit helm_install? +

Yes. Add a rate_limit block to the helm_install 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.

How do I block helm_install completely? +

Set action: deny in the PolicyLayer policy for helm_install. 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.

What MCP server provides helm_install? +

helm_install 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.