List all URLs currently waiting in the documentation processing queue. Shows pending documentation sources that will be processed when run_queue is called. Use this to monitor queue status, verify URLs were added correctly, or check processing backlog. Returns URLs in the order they will be proce...
AI agents call list_queue to retrieve information from RAG Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about the current state of a processing queue. It performs no mutations, executions, or destructive operations—it only queries and returns existing queue data to enable monitoring. This is a pure read operation with minimal blast radius if misused by an agent, as it cannot alter system state or trigger unwanted actions.
From the tool's definition Tool description states it 'List all URLs currently waiting' and 'Shows pending documentation sources' with 'Returns URLs in the order they will be processed.' The verb 'list' and 'show' indicate read-only retrieval of queue status with no modification or…
Attacks that exploit this kind of access
List all URLs currently waiting in the documentation processing queue. Shows pending documentation sources that will be processed when run_queue is called. Use this to monitor queue status, verify URLs were added correctly, or check processing backlog. Returns URLs in the order they will be processed. It is categorised as a Read tool in the RAG Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RAG Documentation MCP Server MCP server in PolicyLayer and add a rule for list_queue: 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 RAG Documentation MCP Server. Nothing to install.
list_queue 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 list_queue 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 list_queue. 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.
list_queue is provided by the RAG Documentation MCP Server MCP server (jumasheff/mcp-ragdoc-fork). 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 →