AI agents call lidarr.system_status to retrieve information from Arr Stack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve Lidarr system status information without modifying state. Despite the empty description lowering confidence slightly, the consistent pattern of sibling tools being informational queries and the 'status' terminology (not 'update', 'set', 'delete', etc.) strongly suggests a Read operation with no side effects.
From the tool's definition Tool name 'system_status' indicates querying system information; the description is empty but the naming pattern ('system_info', 'users_list', 'now_playing', 'library_search') across sibling tools all perform read-only operations.
Attacks that exploit this kind of access
lidarr.system_status. It is categorised as a Read tool in the Arr Stack MCP Server, which means it retrieves data without modifying state.
Register the Arr Stack MCP server in PolicyLayer and add a rule for lidarr.system_status: 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.system_status 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.system_status 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.system_status. 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.system_status 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 →