AI agents call lidarr_list_artists 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 read-only query of the Lidarr media library, returning metadata about artists, albums, and disk usage. There are no side effects, no data modification, and no code execution involved. The blast radius of misuse is minimal—an AI agent calling this tool repeatedly would at worst generate excessive queries against the Lidarr service, but no data would be altered or deleted.
From the tool's definition Tool name 'lidarr_list_artists' and description 'List all artists in the Lidarr library with album counts and disk usage' indicate a retrieval operation that queries existing data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List all artists in the Lidarr library with album counts and disk usage. 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_list_artists: 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_list_artists 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_list_artists 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_list_artists. 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_list_artists 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 →