This record as markdown: /tools/rsp2k-mcp-vultr/convert-instance-ip.md
What convert_instance_ip does on Vultr MCP
AI agents use convert_instance_ip to create or update resources in Vultr MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vultr MCP environment.
Why convert_instance_ip is rated Medium
The tool converts or modifies an instance's IP address assignment, which is a data modification (Write category) rather than destructive, as IP changes are typically reversible. Confidence is moderate due to the missing description; if the tool can forcibly reassign IPs causing service disruption, severity could escalate to high.
From the tool's definition Tool name 'convert_instance_ip' suggests modifying instance IP configuration. With empty description, inferred from context: sibling tools like 'add_ip_whitelist_entry' and 'add_export' indicate this server performs infrastructure modifications.
Attacks that exploit this kind of access
The rule that runs convert_instance_ip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_instance_ip, this is the rule to start with:
convert_instance_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 Vultr MCP, apply this rule, and every convert_instance_ip call is checked against it from then on.
Questions about convert_instance_ip
convert_instance_ip is a write tool on the Vultr MCP server. It is categorised as a Write tool in the Vultr MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vultr MCP server in PolicyLayer and add a rule for convert_instance_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 Vultr MCP. Nothing to install.
convert_instance_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 convert_instance_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 convert_instance_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.
convert_instance_ip is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue