Delete a subscription page configuration
AI agents call sub_page_configs_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.
Deletion of subscription page configurations cannot be undone and removes configuration state that may affect multiple users or subscriptions. This is destructive in nature. While not directly financial, the high-confidence evidence of irreversible data removal places this firmly in the Destructive category rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete a subscription page configuration' — this irreversibly removes data without possibility of recovery through normal operations.
Documented attack patterns abuse exactly the kind of access sub_page_configs_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 sub_page_configs_delete:
{
"version": "1",
"default": "deny",
"hide": [
"sub_page_configs_delete"
]
}sub_page_configs_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 subscription page configuration. 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 sub_page_configs_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.
sub_page_configs_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 sub_page_configs_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 sub_page_configs_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.
sub_page_configs_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.