Scale a ReplicaSet to a specific number of replicas
AI agents invoke scale_replicaset 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.
Scaling a ReplicaSet is an operational action that changes the number of active pod replicas in a Kubernetes cluster. While not destructive (replicas can be scaled back up) or financial, it executes a command that modifies infrastructure state and can cause cascading effects—reducing replicas could interrupt service availability, while increasing replicas consumes resources.
From the tool's definition Tool name 'scale_replicaset' and description 'Scale a ReplicaSet to a specific number of replicas' indicate this performs a container orchestration operation that alters running workloads.
Attacks that exploit this kind of access
Scale a ReplicaSet to a specific number of replicas. 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.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for scale_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.
scale_replicaset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scale_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.
Set action: deny in the PolicyLayer policy for scale_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.
scale_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →