rollout-restart · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What rollout-restart does on Kubernetes MCP Server

AI agents invoke rollout-restart 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 rollout-restart needs a policy

This tool triggers an external operation (Kubernetes rollout restart) whose effects depend on arguments (which deployment to restart). While not destructive (rollouts are reversible), restarting a deployment causes immediate pod termination and replacement, disrupting running services. This is an Execute category risk because it performs an action with operational side effects beyond data modification.

From the tool's definition Tool name 'rollout-restart' and description 'Restart a deployment by triggering a rollout' indicate execution of a Kubernetes rollout operation that restarts pods in a deployment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rollout-restart Rate-limited

rollout-restart 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": {
    "rollout-restart": {
      "limits": [
        {
          "counter": "rollout-restart_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 rollout-restart

What does the rollout-restart tool do? +

Restart a deployment by triggering a rollout. 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 rollout-restart? +

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

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

Can I rate-limit rollout-restart? +

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

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

rollout-restart 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.