Remove an artist from the Lidarr library by Lidarr artist ID.
AI agents call lidarr_remove_artist 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.
Removing an artist from Lidarr permanently deletes associated metadata, music files, and library entries. This action cannot be undone and represents irreversible data loss. While the blast radius is limited to the Lidarr service rather than critical infrastructure, the destructive nature and potential for accidental or malicious removal of large portions of a music library justifies 'high' severity.
From the tool's definition Tool name explicitly states 'remove' and description confirms it 'Remove[s] an artist from the Lidarr library' — this irreversibly deletes data from the media library.
Attacks that exploit this kind of access
Remove an artist from the Lidarr library by Lidarr artist ID. 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 lidarr_remove_artist: 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.
lidarr_remove_artist 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 lidarr_remove_artist 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 lidarr_remove_artist. 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.
lidarr_remove_artist 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 →