k8s_restart_deployment · Kubernetes MCP Server MCP

WHAT IT DOES

What k8s_restart_deployment does on Kubernetes MCP Server

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

This tool executes a Kubernetes control plane operation that terminates and recreates pods in a deployment. While rolling restarts are reversible and do not permanently delete data, the action is a command execution with operational side effects (service interruption, traffic rerouting) that depend on the deployment argument.

From the tool's definition Tool name 'k8s_restart_deployment' and description 'Perform a rolling restart of a deployment' indicate execution of a cluster operation that triggers external effects (pod termination and recreation).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k8s_restart_deployment Rate-limited

k8s_restart_deployment 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": {
    "k8s_restart_deployment": {
      "limits": [
        {
          "counter": "k8s_restart_deployment_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 k8s_restart_deployment

What does the k8s_restart_deployment tool do? +

Perform a rolling restart of a deployment. 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 k8s_restart_deployment? +

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

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

Can I rate-limit k8s_restart_deployment? +

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

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

k8s_restart_deployment is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.