remove_balancer_ips
Удаляет backend IP-адреса у балансировщика (снимает их из распределения трафика).
This record as markdown: /tools/timeweb-mcp/remove-balancer-ips.md
What remove_balancer_ips does on Timeweb
AI agents call remove_balancer_ips 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 |
|---|---|---|---|
ips | array | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - массив backend IP-адресов для удаления |
balancer_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID балансировщика |
Parameters from the server's own tool schema.
Why remove_balancer_ips is rated Critical
This tool permanently removes IP addresses from a load balancer configuration, which cannot be undone without re-adding them through separate operations. This is an irreversible infrastructure modification that could disrupt service traffic routing.
From the tool's definition Tool name 'remove_balancer_ips' combined with description 'Удаляет backend IP-адреса у балансировщика' (removes backend IP addresses from balancer) indicates irreversible deletion of load balancer configuration.
Attacks that exploit this kind of access
The rule that runs remove_balancer_ips 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 remove_balancer_ips, this is the rule to start with:
remove_balancer_ips 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 remove_balancer_ips call is checked against it from then on.
Questions about remove_balancer_ips
Удаляет backend IP-адреса у балансировщика (снимает их из распределения трафика). 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.
remove_balancer_ips accepts 2 parameters: ips, balancer_id. Required: ips, 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 remove_balancer_ips: 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.
remove_balancer_ips 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 remove_balancer_ips 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 remove_balancer_ips. 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.
remove_balancer_ips 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