AI agents invoke system_srr_matcher 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.
The tool tests/executes subscription request routing rules, which involves running logic against routing configurations. This is an Execute-category action as it triggers evaluation of routing rules. Severity is medium since misconfiguration could affect VPN subscription routing, but the description implies a test/diagnostic function rather than persistent changes.
From the tool's definition 'Test subscription request routing rules' — testing/executing routing rule matching logic
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_srr_matcher 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 system_srr_matcher:
{
"version": "1",
"default": "deny",
"tools": {
"system_srr_matcher": {
"limits": [
{
"counter": "system_srr_matcher_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}system_srr_matcher 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.
Test subscription request routing rules. 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 system_srr_matcher: 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.
system_srr_matcher 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 system_srr_matcher 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 system_srr_matcher. 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.
system_srr_matcher 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.