add_torrent · Transmission MCP: Risk & Policy

WHAT IT DOES

What add_torrent does on Transmission

AI agents use add_torrent to create or update resources in Transmission — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Transmission environment.

WHY IT NEEDS A POLICY

Why add_torrent needs a policy

This is a Write operation because it creates/adds a new torrent to the transmission queue, modifying the client's state reversibly. While the actual download consequences depend on torrent content, the tool itself performs data creation rather than deletion or code execution.

From the tool's definition Tool description states 'Add a torrent' which creates a new torrent entry in the transmission client. The tool accepts magnet links, HTTP URLs, or file paths as input, initiating a download/addition operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_torrent Rate-limited

add_torrent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_torrent": {
      "limits": [
        {
          "counter": "add_torrent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about add_torrent

What does the add_torrent tool do? +

Add a torrent from magnet link, HTTP URL, or local file path. It is categorised as a Write tool in the Transmission MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_torrent? +

Register the Transmission MCP server in PolicyLayer and add a rule for add_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 Transmission. Nothing to install.

What risk level is add_torrent? +

add_torrent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_torrent? +

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

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

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