list_balancer_rules
Возвращает список правил балансировщика — соответствий между портом балансировщика и портом backend-сервера.
This record as markdown: /tools/timeweb-mcp/list-balancer-rules.md
What list_balancer_rules does on Timeweb
AI agents call list_balancer_rules to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
balancer_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID балансировщика |
Parameters from the server's own tool schema.
Why list_balancer_rules is rated Low
This tool queries and returns existing balancer rule mappings between load balancer ports and backend server ports. It is purely informational and does not create, modify, delete, or execute anything. It falls squarely in the Read category with low severity since unauthorized access to load balancer configuration could reveal infrastructure details, but the blast radius is limited to information disclosure.
From the tool's definition Tool name 'list_balancer_rules' and description state it 'Возвращает список правил балансировщика' (returns a list of load balancer rules) — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_balancer_rules 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 list_balancer_rules, this is the rule to start with:
list_balancer_rules is read-only, so it stays allowed. 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 list_balancer_rules call is checked against it from then on.
Questions about list_balancer_rules
Возвращает список правил балансировщика — соответствий между портом балансировщика и портом backend-сервера. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
list_balancer_rules accepts 1 parameter: 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 list_balancer_rules: 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.
list_balancer_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_balancer_rules 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 list_balancer_rules. 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.
list_balancer_rules 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