Remove a torrent. Set delete_data=True to also delete downloaded files.
AI agents call remove_torrent to permanently remove resources in Transmission — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes torrents and can irreversibly delete associated downloaded data when the delete_data flag is set to True. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is limited to torrent data rather than critical systems, the irreversible nature and user intent to delete files justifies 'high'…
From the tool's definition Tool description states 'Remove a torrent' with option to 'delete downloaded files' via delete_data=True parameter. This is an irreversible deletion operation.
Attacks that exploit this kind of access
Remove a torrent. Set delete_data=True to also delete downloaded files. It is categorised as a Destructive tool in the Transmission MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Transmission MCP server in PolicyLayer and add a rule for remove_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.
remove_torrent is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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 →