Clear all entries from the Sonarr blocklist.
AI agents call sonarr_clear_blocklist to permanently remove resources in Homelab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes all entries from Sonarr's blocklist in a single bulk operation. There is no indication of a recovery or undo mechanism, making it a destructive action. Misuse could cause Sonarr to re-attempt downloading previously blocked (unwanted or malicious) releases, potentially filling storage or downloading bad content.
From the tool's definition 'Clear all entries from the Sonarr blocklist' — bulk removal of all blocklist entries is irreversible
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all entries from the Sonarr blocklist. It is categorised as a Destructive tool in the Homelab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Homelab MCP server in PolicyLayer and add a rule for sonarr_clear_blocklist: 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.
sonarr_clear_blocklist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sonarr_clear_blocklist 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 sonarr_clear_blocklist. 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.
sonarr_clear_blocklist 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 →