AI agents use set_torrent_download_limit to create or update resources in qBittorrent MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your qBittorrent MCP environment.
This tool modifies a torrent's properties (download speed limit) in a reversible manner. It is not destructive since the limit can be changed again or removed. It is not Execute since it does not run code or arbitrary operations—it configures a specific qBittorrent parameter. It is Write-category because it creates or modifies settings that control torrent behavior.
From the tool's definition Tool name and description: "set_torrent_download_limit" with description "Set torrent download speed limit". This modifies a torrent's configuration setting (download speed limit) but does not delete data or execute arbitrary commands.
Documented attack patterns abuse exactly the kind of access set_torrent_download_limit 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 set_torrent_download_limit:
{
"version": "1",
"default": "deny",
"tools": {
"set_torrent_download_limit": {
"limits": [
{
"counter": "set_torrent_download_limit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_torrent_download_limit 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.
Free to start. No card required.
Set torrent download speed limit. It is categorised as a Write tool in the qBittorrent MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the qBittorrent MCP server in PolicyLayer and add a rule for set_torrent_download_limit: 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.
set_torrent_download_limit 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 set_torrent_download_limit 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 set_torrent_download_limit. 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.
set_torrent_download_limit 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.