AI agents call billing_node_delete 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.
The tool permanently removes billing node data without the ability to undo the operation. Given this is part of a VPN panel administration system managing subscriptions and billing, deletion of a billing node could disrupt payment processing, subscriber access, and financial records. This is irreversible data destruction in a financial context, warranting the highest severity classification.
From the tool's definition Tool name 'billing_node_delete' combined with description 'Delete a billing node' explicitly performs a delete operation on a billing entity, which is an irreversible action.
Documented attack patterns abuse exactly the kind of access billing_node_delete 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_node_delete:
{
"version": "1",
"default": "deny",
"hide": [
"billing_node_delete"
]
}billing_node_delete 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.
Delete a billing 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 billing_node_delete: 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_node_delete 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 billing_node_delete 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_node_delete. 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_node_delete 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.