AI agents use set_torrent_upload_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 changes torrent settings in a reversible manner. While it affects torrent behavior, the change can be undone by setting a different limit or resetting to defaults. The blast radius is medium because misconfiguring upload limits could degrade network performance or violate ISP terms, but the operation itself is not destructive or financial in nature.
From the tool's definition The tool 'set_torrent_upload_limit' modifies torrent configuration by adjusting upload speed parameters. This is a reversible modification operation, not a read-only query (unlike get_torrent_list or get_application_version) and not destructive (unlike…
Documented attack patterns abuse exactly the kind of access set_torrent_upload_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_upload_limit:
{
"version": "1",
"default": "deny",
"tools": {
"set_torrent_upload_limit": {
"limits": [
{
"counter": "set_torrent_upload_limit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_torrent_upload_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 upload 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_upload_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_upload_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_upload_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_upload_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_upload_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.