Get information about torrents in qBittorrent.
AI agents call get_torrent_info to retrieve information from qBittorrent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about existing torrents (status, progress, peers, etc.) without altering state or triggering actions. It is a pure query operation analogous to 'get' or 'fetch' in the Read category. The server's other tools (delete_torrent, download_torrent, pause_torrent, resume_torrent) are more invasive; this one is informationally benign.
From the tool's definition Tool name 'get_torrent_info' and description 'Get information about torrents in qBittorrent' indicate a retrieval operation with no modification or side effects. No mention of downloading, deleting, pausing, or modifying torrents.
Attacks that exploit this kind of access
Get information about torrents in qBittorrent. It is categorised as a Read tool in the qBittorrent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the qBittorrent MCP Server MCP server in PolicyLayer and add a rule for get_torrent_info: 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.
get_torrent_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_torrent_info 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 get_torrent_info. 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.
get_torrent_info 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 →