Scale a deployment to a specific number of replicas
AI agents invoke k8s_scale_deployment 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.
This tool executes commands that modify Kubernetes deployment replicas, causing immediate infrastructure changes whose effects depend on the numeric argument (replica count) provided. While not destructive (reversible by rescaling) or financial, it actively executes operational changes affecting cluster state and resource utilization.
From the tool's definition Tool name 'k8s_scale_deployment' with description 'Scale a deployment to a specific number of replicas' performs operational execution that triggers external effects on Kubernetes infrastructure.
Attacks that exploit this kind of access
Scale a deployment 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 k8s_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.
k8s_scale_deployment 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 k8s_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 k8s_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.
k8s_scale_deployment is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). 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 →