Get details for a specific torrent by its ID or infohash.
AI agents call get_torrent_details to retrieve information from rqbit Torrent Client MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a retrieval operation only—it fetches and returns metadata about a torrent without creating, modifying, deleting, or executing any operations. This is a classic Read category operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_torrent_details' and description states it retrieves information: 'Get details for a specific torrent by its ID or infohash.' This is a query/lookup operation with no modification or execution of external actions.
Attacks that exploit this kind of access
Get details for a specific torrent by its ID or infohash. It is categorised as a Read tool in the rqbit Torrent Client MCP MCP Server, which means it retrieves data without modifying state.
Register the rqbit Torrent Client MCP server in PolicyLayer and add a rule for get_torrent_details: 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 rqbit Torrent Client MCP. Nothing to install.
get_torrent_details 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_details 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_details. 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_details is provided by the rqbit Torrent Client MCP server (philogicae/rqbit-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 →