AI agents call lidarr_search_artist to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation that queries a music database (Lidarr/MusicBrainz) and returns results. It has no side effects—it does not create, modify, delete, or execute any actions. The description explicitly states it 'returns' data, confirming it is a read-only retrieval operation. The mention of use 'before lidarr_add_artist' further confirms this is a prerequisite lookup step with no state changes.
From the tool's definition Tool name 'lidarr_search_artist' and description 'Search for a music artist by name. Returns MusicBrainz IDs and album counts.' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
Search for a music artist by name. Returns MusicBrainz IDs and album counts. Use before lidarr_add_artist. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for lidarr_search_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_search_artist is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lidarr_search_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_search_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_search_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 →