AI agents use add_trackers_to_torrent 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 creates or modifies torrent metadata by adding trackers, which is a write operation. It has medium severity because while tracker modification can affect torrent operation and potentially be used to redirect traffic, it's reversible and doesn't delete data or execute arbitrary code. The blast radius is limited to altering torrent peer discovery mechanisms.
From the tool's definition add_trackers_to_torrent adds new trackers to a torrent, which modifies the torrent's configuration and metadata.
Documented attack patterns abuse exactly the kind of access add_trackers_to_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 add_trackers_to_torrent:
{
"version": "1",
"default": "deny",
"tools": {
"add_trackers_to_torrent": {
"limits": [
{
"counter": "add_trackers_to_torrent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_trackers_to_torrent 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.
Add trackers to torrent. 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 add_trackers_to_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.
add_trackers_to_torrent 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 add_trackers_to_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 add_trackers_to_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.
add_trackers_to_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.