update_balancer
Обновляе�� параметры существующего балансировщика. Все поля кроме balancer_id — опциональные; передавай только то, что меняется.
This record as markdown: /tools/timeweb-mcp/update-balancer.md
What update_balancer does on Timeweb
AI agents use update_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 | — | Алгоритм (опц.) |
fall | number | — | Порог ошибок (опц.) |
name | string | — | Новое имя (опц.) |
path | string | — | Путь (опц.) |
port | number | — | Порт (опц.) |
rise | number | — | Порог успешных (опц.) |
inter | number | — | Интервал проверки (опц.) |
proto | string | — | Протокол (опц.) |
is_ssl | boolean | — | Перенаправление на SSL (опц.) |
comment | string | — | Комментарий (опц.) |
maxconn | number | — | Макс. соединений (опц.) |
timeout | number | — | Таймаут ответа (опц.) |
Parameters from the server's own tool schema.
Why update_balancer is rated Medium
An AI agent can call update_balancer faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (path) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_balancer, this is the rule to start with:
update_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 update_balancer call is checked against it from then on.
Questions about update_balancer
Обновляе�� параметры существующего балансировщика. Все поля кроме balancer_id — опциональные; передавай только то, что меняется. 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.
update_balancer accepts 12 parameters: algo, fall, name, path, port, rise, inter, proto, is_ssl, comment, maxconn, timeout. 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 update_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.
update_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 update_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 update_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.
update_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