AI agents invoke k8s_scale_deployment to trigger actions in Infra Ops. 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 an operation that modifies infrastructure state by changing deployment replica counts. While the action itself is reversible (scale up or down), it triggers real-world effects on running systems, making it Execute rather than Write. Misuse could cause denial-of-service via scaling to zero, performance degradation, or unexpected infrastructure behavior.
From the tool's definition Tool name 'k8s_scale_deployment' and description 'Scale a Kubernetes deployment to the specified number of replicas' indicates execution of infrastructure operations that trigger external system changes (scaling Kubernetes deployments).
Attacks that exploit this kind of access
Scale a Kubernetes deployment to the specified number of replicas. It is categorised as a Execute tool in the Infra Ops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infra Ops 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 Infra Ops. 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 Infra Ops MCP server (skyvanguard/infra-ops-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 →