create_replicaset · Kubernetes MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_replicaset does on Kubernetes MCP Server

AI agents use create_replicaset to create or update resources in Kubernetes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kubernetes MCP Server environment.

WHY IT NEEDS A POLICY

Why create_replicaset needs a policy

Creating a ReplicaSet is a reversible write operation that instantiates new Kubernetes resources and can spawn multiple pod replicas consuming cluster resources. While not destructive (it can be deleted) and not immediately executing arbitrary code, it is a write operation with significant blast radius if misused by an agent—it could exhaust cluster resources or deploy unintended workloads.

From the tool's definition Tool name is 'create_replicaset' and description states 'Create a new ReplicaSet'. The verb 'create' indicates data creation. ReplicaSets manage pod replicas in Kubernetes, making this a write operation that creates new infrastructure resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_replicaset Rate-limited

create_replicaset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_replicaset": {
      "limits": [
        {
          "counter": "create_replicaset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_replicaset

What does the create_replicaset tool do? +

Create a new ReplicaSet. It is categorised as a Write tool in the Kubernetes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_replicaset? +

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

create_replicaset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_replicaset? +

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

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

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