increase_k8s_node_group_nodes
Добавляет указанное количество воркер-нод в группу. Опционально назначает лейблы новым нодам.
This record as markdown: /tools/timeweb-mcp/increase-k8s-node-group-nodes.md
What increase_k8s_node_group_nodes does on Timeweb
AI agents use increase_k8s_node_group_nodes to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - количество добавляемых нод |
labels | array | — | Лейблы для добавляемых нод |
group_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID группы нод |
cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера |
Parameters from the server's own tool schema.
Why increase_k8s_node_group_nodes is rated Medium
This tool creates new worker nodes in a Kubernetes node group, which is a Write operation (provisioning new resources). It is reversible in that nodes can later be removed. Severity is high because spinning up additional nodes incurs infrastructure costs and changes cluster capacity, potentially impacting workloads and billing.
From the tool's definition Добавляет указанное количество воркер-нод в группу — 'adds specified number of worker nodes to a group'
Attacks that exploit this kind of access
The rule that runs increase_k8s_node_group_nodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For increase_k8s_node_group_nodes, this is the rule to start with:
increase_k8s_node_group_nodes 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every increase_k8s_node_group_nodes call is checked against it from then on.
Questions about increase_k8s_node_group_nodes
Добавляет указанное количество воркер-нод в группу. Опционально назначает лейблы новым нодам. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
increase_k8s_node_group_nodes accepts 4 parameters: count, labels, group_id, cluster_id. Required: count, group_id, cluster_id. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for increase_k8s_node_group_nodes: 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 Timeweb. Nothing to install.
increase_k8s_node_group_nodes 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 increase_k8s_node_group_nodes 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 increase_k8s_node_group_nodes. 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.
increase_k8s_node_group_nodes is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue