scale_deployment · K8s MCP: Risk & Policy

WHAT IT DOES

What scale_deployment does on K8s

AI agents invoke scale_deployment to trigger actions in K8s. 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 scale_deployment needs a policy

Scaling a deployment is an Execute action because it triggers external operations (modifying the Kubernetes cluster state) whose blast radius depends on the replica count argument—a misconfigured scale-up could exhaust resources or create instability; a scale-down could cause service disruption.

From the tool's definition Tool name: scale_deployment. Description: 'Scale a deployment to the specified replica count.' This modifies the number of running Kubernetes pod replicas, which is an operational action that affects live infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scale_deployment Rate-limited

scale_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": {
    "scale_deployment": {
      "limits": [
        {
          "counter": "scale_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 K8s, so you can run agents against it safely.

FAQ

Questions about scale_deployment

What does the scale_deployment tool do? +

Scale a deployment to the specified replica count. It is categorised as a Execute tool in the K8s MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scale_deployment? +

Register the K8s MCP server in PolicyLayer and add a rule for scale_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 K8s. Nothing to install.

What risk level is scale_deployment? +

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

Can I rate-limit scale_deployment? +

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

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

scale_deployment is provided by the K8s MCP server (jingyanjiang/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.