lidarr.artist_delete
AI agents call lidarr.artist_delete to permanently remove resources in Arr Stack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a destructive operation (delete) that permanently removes artist data from the Lidarr music library. This cannot be undone and represents data loss. Despite the empty description, the function name unambiguously indicates a destructive action. Lidarr is a media management system where deletions of artists and associated metadata are irreversible operations.
From the tool's definition Tool name 'lidarr.artist_delete' explicitly indicates deletion of artist records. The 'delete' operation on a music library management system (Lidarr) is inherently destructive and irreversible.
Attacks that exploit this kind of access
lidarr.artist_delete. It is categorised as a Destructive tool in the Arr Stack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Arr Stack MCP server in PolicyLayer and add a rule for lidarr.artist_delete: 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 Arr Stack. Nothing to install.
lidarr.artist_delete 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.artist_delete 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.artist_delete. 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.artist_delete is provided by the Arr Stack MCP server (new-usemame/arr-stack-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 →