AI agents call stack.queue_status_all 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 name contains 'status' and 'queue', which typically denote read-only monitoring operations. Despite the empty description, the pattern of sibling tools and the semantic meaning of 'queue_status_all' as a status check (not an action that modifies state) classifies this as a Read operation with low severity.
From the tool's definition Tool name 'queue_status_all' indicates a status query operation; sibling tools follow patterns like 'search', 'list', 'info', 'now_playing' (all Read operations) and 'scan_library', 'add', 'delete' (which are explicitly Write/Destructive).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
stack.queue_status_all. 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 stack.queue_status_all: 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.
stack.queue_status_all 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 stack.queue_status_all 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 stack.queue_status_all. 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.
stack.queue_status_all 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 →