add_balancer_to_project
Привязывает существующий балансировщик к проекту. Для переноса между проектами используй transfer_project_resource.
This record as markdown: /tools/timeweb-mcp/add-balancer-to-project.md
What add_balancer_to_project does on Timeweb
AI agents use add_balancer_to_project 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 |
|---|---|---|---|
project_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID проекта, куда добавить балансировщик |
resource_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID балансировщика |
Parameters from the server's own tool schema.
Why add_balancer_to_project is rated Medium
This tool modifies the project structure by associating a load balancer resource with a project, which is a reversible data modification. While it doesn't delete or move data permanently (the description notes transfer_project_resource should be used for transfers), it does change the state of infrastructure organization.
From the tool's definition Tool name 'add_balancer_to_project' and description 'binds an existing load balancer to a project' indicate a modification operation that creates or updates a resource association.
Attacks that exploit this kind of access
The rule that runs add_balancer_to_project 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 add_balancer_to_project, this is the rule to start with:
add_balancer_to_project 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 add_balancer_to_project call is checked against it from then on.
Questions about add_balancer_to_project
Привязывает существующий балансировщик к проекту. Для переноса между проектами используй transfer_project_resource. 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.
add_balancer_to_project accepts 2 parameters: project_id, resource_id. Required: project_id, resource_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 add_balancer_to_project: 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.
add_balancer_to_project 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 add_balancer_to_project 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 add_balancer_to_project. 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.
add_balancer_to_project 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