Delete a torrent from qBittorrent.
AI agents call delete_torrent to permanently remove resources in qBittorrent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a torrent removes it permanently from qBittorrent and cannot be undone. This is a destructive operation that irreversibly removes data, placing it in the Destructive category rather than Write (which is reversible). The severity is high because an AI agent with misuse could remove torrents the user intended to keep, causing data loss.
From the tool's definition Tool name is 'delete_torrent' with description 'Delete a torrent from qBittorrent.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a torrent from qBittorrent. It is categorised as a Destructive tool in the qBittorrent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the qBittorrent MCP Server 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 Server. 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 MCP server (jabberjabberjabber/qbit-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 →