Low Risk

node_plugins_torrent_reports

Get torrent blocker reports

How to control node_plugins_torrent_reports ↓

AI agents call node_plugins_torrent_reports to retrieve information from Remnawave without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves reporting data about torrent blocking activity. The verb 'Get' and the nature of 'reports' (which are informational outputs) indicate a read-only operation that queries existing data without modification, deletion, or execution of commands. The low severity reflects minimal security impact from unauthorized access to this monitoring/reporting data.

From the tool's definition Tool name 'node_plugins_torrent_reports' with description 'Get torrent blocker reports' indicates a query/retrieval operation with no side effects.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "node_plugins_torrent_reports": {}
  }
}

node_plugins_torrent_reports is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the node_plugins_torrent_reports tool do? +

Get torrent blocker reports. It is categorised as a Read tool in the Remnawave MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on node_plugins_torrent_reports? +

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

node_plugins_torrent_reports is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit node_plugins_torrent_reports? +

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

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

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