Create a new IPv4 address for an instance.
AI agents use create_ipv4 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.
This tool creates a new IPv4 address, which is a reversible write operation on cloud infrastructure. It modifies instance networking configuration but does not delete data or execute arbitrary code. Severity is medium because misconfigured IP allocation could cause service disruptions or unexpected infrastructure costs, but the action is recoverable by deleting the created IP address.
From the tool's definition Tool name 'create_ipv4' and description 'Create a new IPv4 address for an instance' indicate resource creation/modification.
Documented attack patterns abuse exactly the kind of access create_ipv4 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_ipv4:
{
"version": "1",
"default": "deny",
"tools": {
"create_ipv4": {
"limits": [
{
"counter": "create_ipv4_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_ipv4 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.
Free to start. No card required.
Create a new IPv4 address for an instance. 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 create_ipv4: 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.
create_ipv4 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 create_ipv4 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 create_ipv4. 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.
create_ipv4 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.
Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.