This record as markdown: /tools/timeweb-mcp/unbind-floating-ip.md
What unbind_floating_ip does on Timeweb
AI agents use unbind_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 |
|---|---|---|---|
floating_ip_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID плавающего IP |
Parameters from the server's own tool schema.
Why unbind_floating_ip is rated Medium
This tool removes an association between a floating IP and a service. It is a reversible modification — the IP can be re-bound later — so it falls under Write rather than Destructive. However, misuse could cause network disruption (e.g., service becomes unreachable), making the severity medium.
From the tool's definition Отвязывает плавающий IP от текущего сервиса (unbinds/detaches a floating IP from the current service)
Attacks that exploit this kind of access
The rule that runs unbind_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 unbind_floating_ip, this is the rule to start with:
unbind_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 unbind_floating_ip call is checked against it from then on.
Questions about unbind_floating_ip
Отвязывает плавающий IP от текущего сервиса. 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.
unbind_floating_ip accepts 1 parameter: floating_ip_id. Required: 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 unbind_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.
unbind_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 unbind_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 unbind_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.
unbind_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