AI agents call radarr_search_movie 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 queries a movie database (TMDB) and returns informational results. It performs no state changes, does not execute commands, does not delete data, and does not involve financial transactions. This is a straightforward search/lookup operation, which fits the Read category. Severity is low because misuse (e.g., searching for non-existent movies) causes no harm to the system or data.
From the tool's definition Tool description states it 'Search[es] for a movie by title' and 'Returns TMDB IDs, overviews, and ratings.' These are read-only operations that retrieve data without modification or side effects.
Attacks that exploit this kind of access
Search for a movie by title. Returns TMDB IDs, overviews, and ratings. Use before radarr_add_movie. 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_search_movie: 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_search_movie 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_search_movie 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_search_movie. 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_search_movie 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 →