AI agents use lidarr.artist_add to create or update resources in Arr Stack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Arr Stack environment.
The tool adds an artist to Lidarr's database, which is a write operation that creates data. This is reversible (can be deleted via lidarr.artist_delete), so it falls under Write rather than Destructive. The empty description lowers confidence slightly, but the naming convention and context from sibling tools (artist_delete, artist_search) strongly indicate this creates new artist records.
From the tool's definition Tool name 'lidarr.artist_add' indicates creation of a new artist entry in Lidarr (a music library management system). The 'add' operation creates or modifies data reversibly.
Attacks that exploit this kind of access
lidarr.artist_add. It is categorised as a Write tool in the Arr Stack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Arr Stack MCP server in PolicyLayer and add a rule for lidarr.artist_add: 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_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lidarr.artist_add 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_add. 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_add 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 →