create_balancer
Создаёт новый балансировщик нагрузки. Обязательны: name, algo, is_sticky, is_use_proxy, is_ssl, is_keepalive, proto, path, inter, timeout, fall, rise, preset_id. preset_id получай через list_balancer_presets. Для приватной сети задай network_id. Для SSL — certificate_type.
This record as markdown: /tools/timeweb-mcp/create-balancer.md
What create_balancer does on Timeweb
AI agents use create_balancer 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 |
|---|---|---|---|
algo | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - алгоритм балансировки: roundrobin | leastconn |
fall | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - порог количества ошибок |
name | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - имя балансировщика (уникальное в аккаунте) |
path | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - путь health-check (напр. /) |
port | number | — | Порт балансировщика (опц.) |
rise | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - порог количества успешных ответов |
inter | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - интервал проверки |
proto | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - протокол: http | http2 | https | tcp |
is_ssl | boolean | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - требуется ли перенаправление на SSL |
maxconn | number | — | Максимальное количество соединений (опц.) |
timeout | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - таймаут ответа балансировщика |
is_sticky | boolean | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - сохранять ли сессию |
Parameters from the server's own tool schema.
Why create_balancer is rated Medium
This tool creates a new load balancer resource, which is a reversible write operation. It modifies infrastructure state by adding a new managed resource but does not execute arbitrary code, delete data, or commit financial transactions. The severity is medium because misconfiguration could redirect traffic or cause service disruption, but the action itself is recoverable by deletion.
From the tool's definition Tool name is 'create_balancer' and description states 'Создаёт новый балансировщик нагрузки' (Creates a new load balancer). The action is to create/instantiate a new cloud infrastructure resource with configuration parameters.
Risk signalsAccepts file system path (path) · High parameter count (28 properties)
Attacks that exploit this kind of access
The rule that runs create_balancer 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 create_balancer, this is the rule to start with:
create_balancer 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 create_balancer call is checked against it from then on.
Questions about create_balancer
Создаёт новый балансировщик нагрузки. Обязательны: name, algo, is_sticky, is_use_proxy, is_ssl, is_keepalive, proto, path, inter, timeout, fall, rise, preset_id. preset_id получай через list_balancer_presets. Для приватной сети задай network_id. Для SSL — certificate_type. 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.
create_balancer accepts 12 parameters: algo, fall, name, path, port, rise, inter, proto, is_ssl, maxconn, timeout, is_sticky. Required: algo, fall, name, path, rise, inter, proto, is_ssl, timeout, is_sticky. 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 create_balancer: 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.
create_balancer 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 create_balancer 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 create_balancer. 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.
create_balancer 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