Scale a Kubernetes deployment to a specified number of replicas
AI agents use scale-deployment 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.
Scaling a deployment changes the number of running replicas, which is a reversible modification to cluster state. It can be undone by scaling back. However, misuse (e.g., scaling to 0) could cause service outages, making the blast radius high. It does not permanently delete resources, so Write is the most appropriate category rather than Destructive.
From the tool's definition Scale a Kubernetes deployment to a specified number of replicas
Attacks that exploit this kind of access
Scale a Kubernetes deployment to a specified number of replicas. 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.
Register the Kubernetes MCP Server 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 Kubernetes MCP Server. Nothing to install.
scale-deployment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
scale-deployment is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →