AI agents call sabnzbd_get_history 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 returns information about past downloads (status, size, completion time, failure messages). It is a read-only operation that retrieves data with no capability to modify, delete, or trigger actions. The low severity reflects minimal blast radius even if misused, as viewing download history poses no security or operational risk.
From the tool's definition Tool name contains 'get_history' and description states 'Show recent SABnzbd download history' — retrieves and displays historical download data without modification or side effects.
Attacks that exploit this kind of access
Show recent SABnzbd download history with status, size, completion time, and any failure messages. 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_history: 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_history 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_history 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_history. 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_history 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 →