delete_balancer
Удаляет балансировщик. Действие необратимо. Для аккаунтов с 2FA — первый вызов вернёт hash, повторный вызов с hash и code завершит удаление.
This record as markdown: /tools/timeweb-mcp/delete-balancer.md
What delete_balancer does on Timeweb
AI agents call delete_balancer to permanently remove resources in Timeweb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | Код 2FA из приложения-аутентификатора |
hash | string | — | Hash подтверждения (для аккаунтов с 2FA) |
balancer_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID балансировщика |
Parameters from the server's own tool schema.
Why delete_balancer is rated Critical
An AI agent that decides to call delete_balancer doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Timeweb is gone. There is no undo for destructive operations.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs delete_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 delete_balancer, this is the rule to start with:
delete_balancer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every delete_balancer call is checked against it from then on.
Questions about delete_balancer
Удаляет балансировщик. Действие необратимо. Для аккаунтов с 2FA — первый вызов вернёт hash, повторный вызов с hash и code завершит удаление. It is categorised as a Destructive tool in the Timeweb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_balancer accepts 3 parameters: code, hash, balancer_id. Required: balancer_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 delete_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.
delete_balancer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue