AI agents call billing_nodes_list 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 billing node information without creating, modifying, or deleting data. It is a read-only operation that queries existing data structures, consistent with the 'list' pattern for data retrieval. Listing billing configuration nodes poses minimal security risk as it only exposes information that is typically accessible to administrators within the system.
From the tool's definition Tool name 'billing_nodes_list' and description 'List all billing nodes' indicate a query/retrieval operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access billing_nodes_list 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 billing_nodes_list:
{
"version": "1",
"default": "deny",
"tools": {
"billing_nodes_list": {}
}
}billing_nodes_list 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.
List all billing nodes. 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 billing_nodes_list: 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.
billing_nodes_list 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 billing_nodes_list 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 billing_nodes_list. 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.
billing_nodes_list 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.