AI agents call lidarr_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 retrieves and displays information about active downloads and their status. It performs no modifications, deletions, or external operations—it only reads and reports current queue state from Lidarr. This is a non-destructive, read-only operation with minimal security risk if misused by an agent.
From the tool's definition Tool name 'lidarr_get_queue' and description 'Show active and queued music downloads in Lidarr with progress and ETA' indicate a retrieval operation that queries the state of downloads without modifying data.
Attacks that exploit this kind of access
Show active and queued music downloads in Lidarr 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 lidarr_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.
lidarr_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 lidarr_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 lidarr_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.
lidarr_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 →