k8s_deployment · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What k8s_deployment does on RedisNexus

AI agents invoke k8s_deployment to trigger actions in RedisNexus. 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_deployment needs a policy

While 'inspect' is a read operation, the tool combines it with execute-capable actions: restarting deployments and scaling replicas are imperative operations that modify cluster state and trigger cascading effects (pod termination, service disruptions). Rollback can sometimes undo changes but is still an active operation.

From the tool's definition Tool description states it can 'scale, restart, rollback' Kubernetes deployments. These are operational commands that trigger external actions (pod restarts, replica count changes) whose effects depend on arguments and cannot always be easily reversed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k8s_deployment Rate-limited

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

FAQ

Questions about k8s_deployment

What does the k8s_deployment tool do? +

Manage Kubernetes deployments: inspect, scale, restart, rollback. It is categorised as a Execute tool in the RedisNexus 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_deployment? +

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

What risk level is k8s_deployment? +

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

Can I rate-limit k8s_deployment? +

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

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

k8s_deployment is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.