AI agents call system_nodes_metrics to retrieve information from Remnawave without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries node metrics without creating, modifying, deleting, or executing any operations. It is a passive read-only operation that has no side effects. Even in a VPN administration context, accessing metrics does not pose significant risk as it gathers observational data about system state rather than changing configuration or triggering actions.
From the tool's definition Tool name 'system_nodes_metrics' with description 'Get detailed node metrics' indicates retrieval of metrics data with no modification capability.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_nodes_metrics 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_nodes_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"system_nodes_metrics": {}
}
}system_nodes_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed node metrics. It is categorised as a Read tool in the Remnawave MCP Server, which means it retrieves data without modifying state.
Register the Remnawave MCP server in PolicyLayer and add a rule for system_nodes_metrics: 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_nodes_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the system_nodes_metrics 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_nodes_metrics. 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_nodes_metrics 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.