start_torrent · rqbit Torrent Client MCP: Risk & Policy

WHAT IT DOES

What start_torrent does on rqbit Torrent Client MCP

AI agents invoke start_torrent to trigger actions in rqbit Torrent Client MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_torrent needs a policy

This tool executes an action (torrent resume) that has observable side effects on the system and network—it initiates data transfer, network connections, and I/O operations. However, it is not Destructive (no data deletion), Financial (no money movement), or Write (not creating/modifying data structures persistently).

From the tool's definition Tool is named 'start_torrent' and described as 'Start (resume) a torrent.' This triggers external network operations (torrent peer connections, file seeding/leeching) whose effects depend on which torrent is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_torrent Rate-limited

start_torrent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_torrent": {
      "limits": [
        {
          "counter": "start_torrent_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches rqbit Torrent Client MCP, so you can run agents against it safely.

FAQ

Questions about start_torrent

What does the start_torrent tool do? +

Start (resume) a torrent. It is categorised as a Execute tool in the rqbit Torrent Client MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_torrent? +

Register the rqbit Torrent Client MCP server in PolicyLayer and add a rule for start_torrent: 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 rqbit Torrent Client MCP. Nothing to install.

What risk level is start_torrent? +

start_torrent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_torrent? +

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

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

start_torrent is provided by the rqbit Torrent Client MCP server (philogicae/rqbit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.