Move torrent data to a new location.
AI agents use move_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.
Moving torrent data modifies the state of the system by relocating files to a new directory, which is a reversible Write operation. While the operation changes data location, it does not permanently delete data (Destructive) or execute arbitrary code (Execute). The severity is medium because a misguided move could cause disk space issues or temporary service disruption, but the operation is reversible.
From the tool's definition Tool name 'move_torrent' and description 'Move torrent data to a new location' indicates modification of file/data location without deletion.
Attacks that exploit this kind of access
Move torrent data to a new location. 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.
Register the Transmission MCP server in PolicyLayer and add a rule for move_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.
move_torrent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_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.
Set action: deny in the PolicyLayer policy for move_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.
move_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →