AI agents use lidarr_add_artist to create or update resources in Homelab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Homelab environment.
This tool creates a new artist entry in Lidarr (a write operation) and triggers an automated search/download process. While it initiates a download, the primary action is adding/creating data in the media management system. It is reversible (the artist can be removed). The automated download search is a side effect but doesn't elevate this to Execute or Destructive.
From the tool's definition Add a music artist to Lidarr and trigger an automatic album download search
Attacks that exploit this kind of access
Add a music artist to Lidarr and trigger an automatic album download search. It is categorised as a Write tool in the Homelab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Homelab MCP server in PolicyLayer and add a rule for lidarr_add_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_add_artist 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_add_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_add_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_add_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 →