search_torrents
AI agents call search_torrents 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 torrent search results from search plugins without modifying, deleting, or executing external operations. It is a read-only retrieval operation. Confidence is 0.85 rather than higher because the tool description is empty, though the context from the server description and tool name provides strong evidence of its read-only nature.
From the tool's definition Tool name 'search_torrents' combined with server description stating it 'search[es] for torrents using search plugins'. No description provided for the tool itself, but the naming and context clearly indicate a query/search operation with no side effects.
Attacks that exploit this kind of access
search_torrents. 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 search_torrents: 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.
search_torrents 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 search_torrents 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 search_torrents. 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.
search_torrents 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 →