AI agents use hosts_bulk_set_inbound 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 modifies/updates configuration data (inbound settings) on multiple hosts in bulk. While reversible (configurations can be changed again), the 'bulk' operation on network-critical infrastructure (VPN panel host management) poses significant blast radius if misapplied—potentially disrupting service availability or redirecting traffic.
From the tool's definition Tool name 'hosts_bulk_set_inbound' and description 'Bulk set inbound for selected hosts' indicates modification of host configurations affecting network inbound settings across multiple hosts simultaneously.
Documented attack patterns abuse exactly the kind of access hosts_bulk_set_inbound 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_bulk_set_inbound:
{
"version": "1",
"default": "deny",
"tools": {
"hosts_bulk_set_inbound": {
"limits": [
{
"counter": "hosts_bulk_set_inbound_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}hosts_bulk_set_inbound 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.
Bulk set inbound for selected hosts. 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_bulk_set_inbound: 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_bulk_set_inbound 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_bulk_set_inbound 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_bulk_set_inbound. 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_bulk_set_inbound 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.