Bulk actions on selected nodes (enable/disable/restart)
AI agents invoke nodes_bulk_actions to trigger actions in Remnawave. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes commands that change system state and trigger operations on VPN infrastructure nodes. While not permanently destructive (enable/disable/restart are theoretically reversible), it controls critical infrastructure and can disrupt service availability. Misuse could disable nodes, causing outages.
From the tool's definition Tool performs 'Bulk actions on selected nodes (enable/disable/restart)' - these are operations that trigger external effects on infrastructure (node restart, enable/disable state changes) whose consequences depend on which nodes are selected.
Documented attack patterns abuse exactly the kind of access nodes_bulk_actions 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 nodes_bulk_actions:
{
"version": "1",
"default": "deny",
"tools": {
"nodes_bulk_actions": {
"limits": [
{
"counter": "nodes_bulk_actions_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} nodes_bulk_actions stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Bulk actions on selected nodes (enable/disable/restart). It is categorised as a Execute tool in the Remnawave MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Remnawave MCP server in PolicyLayer and add a rule for nodes_bulk_actions: 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.
nodes_bulk_actions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the nodes_bulk_actions 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 nodes_bulk_actions. 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.
nodes_bulk_actions 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.