helm-upgrade · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What helm-upgrade does on Kubernetes MCP Server

AI agents invoke helm-upgrade 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-upgrade needs a policy

Upgrading a Helm release is an Execute-level action: it runs Helm operations that redeploy or reconfigure live Kubernetes workloads. While it can be partially reversed via helm rollback, the act itself triggers external operations with variable effects depending on arguments (chart, values, release name). Misuse could disrupt production services, making severity high.

From the tool's definition 'Upgrade a Helm release' — Helm upgrade modifies deployed Kubernetes workloads by changing configuration, chart versions, or values, triggering rollouts and potentially altering running services.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

helm-upgrade Rate-limited

helm-upgrade 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-upgrade": {
      "limits": [
        {
          "counter": "helm-upgrade_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-upgrade

What does the helm-upgrade tool do? +

Upgrade a Helm release. 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-upgrade? +

Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for helm-upgrade: 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-upgrade? +

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

Can I rate-limit helm-upgrade? +

Yes. Add a rate_limit block to the helm-upgrade 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-upgrade completely? +

Set action: deny in the PolicyLayer policy for helm-upgrade. 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-upgrade? +

helm-upgrade 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.