AI agents call nodes_reset_traffic to permanently remove resources in Remnawave — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Resetting a traffic counter is an irreversible destructive action — the historical traffic data for that node is permanently wiped and cannot be recovered. This falls under Destructive rather than Write because the operation overwrites/clears existing data with no way to undo it.
From the tool's definition Reset traffic counter for a node
Documented attack patterns abuse exactly the kind of access nodes_reset_traffic 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_reset_traffic:
{
"version": "1",
"default": "deny",
"hide": [
"nodes_reset_traffic"
]
}nodes_reset_traffic disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Reset traffic counter for a node. It is categorised as a Destructive tool in the Remnawave MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Remnawave MCP server in PolicyLayer and add a rule for nodes_reset_traffic: 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_reset_traffic is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the nodes_reset_traffic 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_reset_traffic. 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_reset_traffic 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.