AI agents use hosts_create to create or update resources in Remnawave — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnawave environment.
This tool creates a new host resource in the Remnawave VPN system. Host creation is a reversible write operation—the resource can be deleted or modified later. While it modifies infrastructure configuration, it is not irreversible (Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions (Financial).
From the tool's definition Tool name 'hosts_create' and description 'Create a new host in Remnawave' indicate data creation/modification. Context shows this is part of a VPN panel management system with 51 administrative tools.
Documented attack patterns abuse exactly the kind of access hosts_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Remnawave, and nothing reaches the server without passing your rules. This is the rule we recommend for hosts_create:
{
"version": "1",
"default": "deny",
"tools": {
"hosts_create": {
"limits": [
{
"counter": "hosts_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}hosts_create 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 host in Remnawave. It is categorised as a Write tool in the Remnawave MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnawave MCP server in PolicyLayer and add a rule for hosts_create: 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 Remnawave. Nothing to install.
hosts_create 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 hosts_create 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 hosts_create. 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.
hosts_create is provided by the Remnawave MCP server (trackline/mcp-remnawave). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 153 Remnawave tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
153 Remnawave tools catalogued and risk-classified — across an index of 42,500+ MCP servers.