AI agents call sabnzbd_get_status 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 and retrieves monitoring/status data from SABnzbd without creating, modifying, deleting, or executing any operations. It has no side effects and presents no risk of unintended state changes. The blast radius of misuse is minimal—an agent could only view system status information, which is inherently safe in a homelab context.
From the tool's definition Tool description explicitly states it 'Show[s]' status information: download speed, remaining data, ETA, disk space, paused state, and queue size. The verb 'Show' indicates read-only retrieval with no modifications.
Attacks that exploit this kind of access
Show SABnzbd global status: download speed, remaining data, ETA, disk space, paused state, and queue size. 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_get_status: 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_get_status 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_get_status 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_get_status. 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_get_status 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 →