AI agents call radarr_check_releases 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 displays information about available movie releases and filtering criteria applied by the Radarr service. It performs no modification, deletion, code execution, or financial transaction. The use case is explicitly debugging/diagnostic in nature ('Use to debug download issues'), confirming it is a Read operation with minimal risk.
From the tool's definition Tool name 'radarr_check_releases' and description 'Show available releases for a movie and why some are being rejected' indicate a query/inspection operation with no side effects.
Attacks that exploit this kind of access
Show available releases for a movie and why some are being rejected. Use to debug download issues. 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 radarr_check_releases: 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.
radarr_check_releases 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 radarr_check_releases 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 radarr_check_releases. 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.
radarr_check_releases 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 →