AI agents call sonarr_interactive_search to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search and retrieval operation against Sonarr's release database, returning information about available TV series episodes/seasons. This is a read-only action with no capability to modify, delete, execute, or create data. The blast radius of misuse is minimal—an AI agent could only retrieve information about available releases, not affect system state or trigger downloads/modifications.
From the tool's definition Tool description states it 'Show[s] all available releases' - a pure retrieval operation that queries and displays data without modification or side effects.
Attacks that exploit this kind of access
Show all available releases for a TV series episode or season with their GUIDs, quality, size, age, indexer, and custom format score. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for sonarr_interactive_search: 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 Homelab. Nothing to install.
sonarr_interactive_search 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 sonarr_interactive_search 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 sonarr_interactive_search. 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.
sonarr_interactive_search is provided by the Homelab MCP server (nainounen/homelab-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 →