AI agents call delete_torrent to permanently remove resources in qBittorrent MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_torrent tool removes torrents, which is a destructive operation that cannot be undone. While the blast radius is somewhat limited (confined to qBittorrent's local state), an AI agent misusing this could permanently remove user torrent records without recovery. This is more severe than Write operations but less than Financial impact, placing it clearly in the Destructive category.
From the tool's definition Tool name 'delete_torrent' combined with description 'Delete torrents from qBittorrent' explicitly indicates irreversible deletion of torrent entries from the system.
Documented attack patterns abuse exactly the kind of access delete_torrent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and qBittorrent MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_torrent:
{
"version": "1",
"default": "deny",
"hide": [
"delete_torrent"
]
}delete_torrent disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete torrents from qBittorrent. It is categorised as a Destructive tool in the qBittorrent MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the qBittorrent MCP server in PolicyLayer and add a rule for delete_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 qBittorrent MCP. Nothing to install.
delete_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 delete_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 delete_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.
delete_torrent is provided by the qBittorrent MCP server (pickpppcc/qbittorrent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from qBittorrent MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 qBittorrent MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.