Critical Risk →

node_plugins_torrent_truncate

Truncate all torrent blocker reports

How to control node_plugins_torrent_truncate ↓

AI agents call node_plugins_torrent_truncate 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

The tool performs an irreversible operation that removes or clears all torrent blocker reports without the ability to undo the action. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The blast radius is high because an agent could permanently lose audit/blocking history data critical for VPN security monitoring and compliance.

From the tool's definition Tool name contains 'truncate' and description states 'Truncate all torrent blocker reports' — truncation is an irreversible deletion or clearing of data records.

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

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

node_plugins_torrent_truncate 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 node_plugins_torrent_truncate tool do? +

Truncate all torrent blocker reports. 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 node_plugins_torrent_truncate? +

Register the Remnawave MCP server in PolicyLayer and add a rule for node_plugins_torrent_truncate: 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 node_plugins_torrent_truncate? +

node_plugins_torrent_truncate 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 node_plugins_torrent_truncate? +

Yes. Add a rate_limit block to the node_plugins_torrent_truncate 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 node_plugins_torrent_truncate completely? +

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

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