Get stats and status for a specific torrent by its ID or infohash.
AI agents call get_torrent_stats 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.
This tool retrieves statistics and status information about a torrent without modifying, deleting, or executing any operations. It has no side effects beyond reading data. The blast radius is minimal—misuse would only expose information about torrents already known to the system.
From the tool's definition Tool name 'get_torrent_stats' and description 'Get stats and status for a specific torrent' indicate a retrieval operation with no state changes. The verb 'Get' and the word 'stats' confirm this is a query function.
Attacks that exploit this kind of access
Get stats and status 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →