bind_floating_ip

Привязывает плавающий IP к сервису (server / balancer / database / network) по ID ресурса

SERVERTimeweb SOURCEtimeweb-mcp

Low RISK CLASS

Category Read

Parameters 33 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/timeweb-mcp/bind-floating-ip.md

WHAT IT DOES

What bind_floating_ip does on Timeweb

AI agents call bind_floating_ip 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
`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.

RISK

Why bind_floating_ip is rated Low

Even though bind_floating_ip only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

bind_floating_ip is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bind_floating_ip": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about bind_floating_ip

What does the bind_floating_ip tool do? +

Привязывает плавающий IP к сервису (server / balancer / database / network) по ID ресурса. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.

What parameters does bind_floating_ip accept? +

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.

How do I enforce a policy on bind_floating_ip? +

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.

What risk level is bind_floating_ip? +

bind_floating_ip is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bind_floating_ip? +

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.

How do I block bind_floating_ip completely? +

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.

What MCP server provides bind_floating_ip? +

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.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →