AI agents call sonarr_list_series 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.
This tool retrieves and queries information about TV series in a media management system (Sonarr). It performs only read operations—listing series, viewing episode counts and download progress, and filtering results. There are no side effects, data modifications, destructive operations, code execution, or financial implications.
From the tool's definition Tool name 'sonarr_list_series' and description 'List TV series in the Sonarr library' indicates data retrieval. The description explicitly states listing, filtering, and searching operations with no mention of modifications, deletions, or command execution.
Attacks that exploit this kind of access
List TV series in the Sonarr library with episode counts and download progress. Supports filtering and search to keep output small. 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_list_series: 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_list_series 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_list_series 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_list_series. 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_list_series 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 →