Get the magnet link for a specific torrent by id.
AI agents call get_magnet_link to retrieve information from Fr Torrent Search 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 information (a magnet link) based on a torrent ID parameter. It has no side effects, does not modify data, does not execute commands, and does not facilitate financial transactions. It is a simple data retrieval operation consistent with the 'Read' category.
From the tool's definition Tool name 'get_magnet_link' and description 'Get the magnet link for a specific torrent by id' indicates retrieval of data. The operation is read-only—it fetches and returns a magnet link without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get the magnet link for a specific torrent by id. It is categorised as a Read tool in the Fr Torrent Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fr Torrent Search MCP Server MCP server in PolicyLayer and add a rule for get_magnet_link: 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 Fr Torrent Search MCP Server. Nothing to install.
get_magnet_link 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_magnet_link 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_magnet_link. 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_magnet_link is provided by the Fr Torrent Search MCP Server MCP server (philogicae/fr-torrent-search-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 →