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 executes a complex set of operations in the cluster: creating deployments, services, configmaps, secrets, RBAC rules, and other Kubernetes resources. This is an Execute-category action with high severity because a misused helm-install could deploy malicious workloads, expose services, grant excessive permissions, or consume significant cluster resources.

From the tool's definition helm-install: 'Install a Helm chart' — installs software/workloads into a Kubernetes cluster, triggering deployment of arbitrary resources

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? +

Install a 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 (thekaranpargaie/kube-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.