List all available search plugins in qBittorrent.
AI agents call list_search_plugins 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 queries and returns information about available search plugins without modifying, creating, deleting, or executing any operations. It is purely informational and has no blast radius if invoked by an AI agent, making it a low-severity Read operation.
From the tool's definition Tool name 'list_search_plugins' and description 'List all available search plugins in qBittorrent' indicate a retrieval operation with no side effects. The verb 'list' is a Read operation that queries existing configuration state.
Attacks that exploit this kind of access
List all available search plugins 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 list_search_plugins: 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.
list_search_plugins 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 list_search_plugins 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 list_search_plugins. 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.
list_search_plugins 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 →