Critical Risk →

snippets_delete

Delete a snippet

How to control snippets_delete ↓

AI agents call snippets_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.

Critical Risk

This tool deletes data and cannot be undone. Deletion is irreversible, placing it in the Destructive category rather than Write. In a VPN panel administration context, deleting snippets (likely code snippets, templates, or configuration fragments) removes them permanently from the system.

From the tool's definition Tool is named 'snippets_delete' with description 'Delete a snippet' — the 'delete' verb indicates irreversible removal of data without recovery option.

Documented attack patterns abuse exactly the kind of access snippets_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 snippets_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "snippets_delete"
  ]
}

snippets_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Remnawave — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the snippets_delete tool do? +

Delete a snippet. 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.

How do I enforce a policy on snippets_delete? +

Register the Remnawave MCP server in PolicyLayer and add a rule for snippets_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.

What risk level is snippets_delete? +

snippets_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit snippets_delete? +

Yes. Add a rate_limit block to the snippets_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.

How do I block snippets_delete completely? +

Set action: deny in the PolicyLayer policy for snippets_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.

What MCP server provides snippets_delete? +

snippets_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.

Enforce policy on every Remnawave tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.