AI agents use users_reset_traffic 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.
Resetting a traffic counter modifies user data (sets counter back to zero), which is a write/update operation. While it overwrites the current traffic value, traffic counters are typically re-accumulating metrics rather than uniquely irreplaceable data, so this is reversible in the sense that the counter will naturally repopulate.
From the tool's definition Reset traffic counter for a Remnawave user
Documented attack patterns abuse exactly the kind of access users_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 users_reset_traffic:
{
"version": "1",
"default": "deny",
"tools": {
"users_reset_traffic": {
"limits": [
{
"counter": "users_reset_traffic_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}users_reset_traffic 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.
Reset traffic counter for a Remnawave user. 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 users_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.
users_reset_traffic 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 users_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 users_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.
users_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.