AI agents call readarr_get_queue 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 queries the status of book downloads in Readarr (a book management application). It retrieves data about downloads in progress and their metadata (progress, ETA) but does not create, modify, delete, or execute operations. The verb 'Show' and the focus on displaying queue information with 'progress and ETA' confirm this is a passive data retrieval operation with no side effects.
From the tool's definition Tool name 'readarr_get_queue' and description 'Show active and queued book downloads' indicate a read-only query operation that retrieves status information without modifying state.
Attacks that exploit this kind of access
Show active and queued book downloads in Readarr with progress and ETA. 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 readarr_get_queue: 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.
readarr_get_queue 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 readarr_get_queue 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 readarr_get_queue. 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.
readarr_get_queue 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 →