Bulk modify config profile for selected nodes
AI agents use nodes_bulk_profile_modification 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 node configuration profiles in bulk across multiple nodes. While it changes data (Write), the modification is reversible (profiles can be reconfigured), distinguishing it from Destructive actions. The 'bulk' aspect elevates severity from medium to high because a single misconfigured call could impact many nodes in a VPN infrastructure, causing widespread service degradation or network issues.
From the tool's definition Tool name contains 'bulk_profile_modification' and description states 'Bulk modify config profile for selected nodes' — indicates mass creation or modification of node configuration data across multiple nodes simultaneously.
Documented attack patterns abuse exactly the kind of access nodes_bulk_profile_modification 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_profile_modification:
{
"version": "1",
"default": "deny",
"tools": {
"nodes_bulk_profile_modification": {
"limits": [
{
"counter": "nodes_bulk_profile_modification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}nodes_bulk_profile_modification 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 modify config profile for selected nodes. 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 nodes_bulk_profile_modification: 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_profile_modification 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 nodes_bulk_profile_modification 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_profile_modification. 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_profile_modification 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.