Clear all entries from the Radarr blocklist so previously rejected releases can be grabbed again.
AI agents call radarr_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 irreversibly removes all blocklist entries in Radarr. 'Clear all entries' is a bulk deletion operation that cannot be undone — once cleared, the historical record of blocked releases is permanently lost, allowing previously rejected releases to be re-downloaded. This fits the Destructive category due to its irreversible bulk deletion nature.
From the tool's definition Clear all entries from the Radarr blocklist so previously rejected releases can be grabbed again
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all entries from the Radarr blocklist so previously rejected releases can be grabbed again. 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 radarr_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.
radarr_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 radarr_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 radarr_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.
radarr_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 →