AI agents call sabnzbd_list_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 in SABnzbd. It performs no side effects, creates no modifications, executes no commands, and deletes nothing. It is purely informational, consistent with Read category tools like 'list' and 'get'. The blast radius of misuse is minimal—an agent could only gain visibility into what is queued for download, which poses low risk.
From the tool's definition Tool name 'sabnzbd_list_queue' and description 'List active SABnzbd download queue with progress, ETA, and category for each NZB' indicate a retrieval/query operation that returns information about download status without modifying or deleting data.
Attacks that exploit this kind of access
List active SABnzbd download queue with progress, ETA, and category for each NZB. 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 sabnzbd_list_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.
sabnzbd_list_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 sabnzbd_list_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 sabnzbd_list_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.
sabnzbd_list_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 →