bind_floating_ip
Привязывает плавающий IP к сервису (server / balancer / database / network) по ID ресурса
This record as markdown: /tools/timeweb-mcp/bind-floating-ip.md
What bind_floating_ip does on Timeweb
AI agents use bind_floating_ip 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 |
|---|---|---|---|
resource_id | string | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID ресурса (число или строка) |
resource_type | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип ресурса: server | balancer | database | network |
floating_ip_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID плавающего IP |
Parameters from the server's own tool schema.
Why bind_floating_ip is rated Medium
This tool binds/associates a floating IP to a service resource. It modifies network configuration (an association), which is reversible (can be unbound), placing it in the Write category. Misuse could disrupt network routing or expose services, hence medium severity.
From the tool's definition Привязывает плавающий IP к сервису (server / balancer / database / network) по ID ресурса
Attacks that exploit this kind of access
The rule that runs bind_floating_ip 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 bind_floating_ip, this is the rule to start with:
bind_floating_ip 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 bind_floating_ip call is checked against it from then on.
Questions about bind_floating_ip
Привязывает плавающий IP к сервису (server / balancer / database / network) по 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.
bind_floating_ip accepts 3 parameters: resource_id, resource_type, floating_ip_id. Required: resource_id, resource_type, floating_ip_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 bind_floating_ip: 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.
bind_floating_ip 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 bind_floating_ip 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 bind_floating_ip. 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.
bind_floating_ip 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