AI agents call users_bulk_delete_by_status 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.
This tool irreversibly deletes user accounts in bulk. Bulk deletion operations cannot be undone and represent loss of data with significant blast radius. Even if backups exist, the operation itself is destructive. The VPN panel context means deleted users lose access and associated subscription data.
From the tool's definition Tool name explicitly contains 'delete' and 'bulk_delete_by_status' performs irreversible deletion of multiple user records based on status criteria.
Documented attack patterns abuse exactly the kind of access users_bulk_delete_by_status 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_bulk_delete_by_status:
{
"version": "1",
"default": "deny",
"hide": [
"users_bulk_delete_by_status"
]
}users_bulk_delete_by_status 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.
Bulk delete users by status. 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 users_bulk_delete_by_status: 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_bulk_delete_by_status 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 users_bulk_delete_by_status 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_bulk_delete_by_status. 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_bulk_delete_by_status 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.