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 is a pure query/retrieval operation that reads queue state. It does not create, modify, delete, execute operations, or incur financial obligations. The only capability is viewing pending documentation sources in read-only fashion.
From the tool's definition Tool description explicitly states it 'List[s] all URLs currently waiting' and 'monitor[s] queue status' without modifying or deleting any data. No side effects mentioned.
Documented attack patterns abuse exactly the kind of access list_queue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAG Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_queue:
{
"version": "1",
"default": "deny",
"tools": {
"list_queue": {}
}
}list_queue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (rahulretnan/mcp-ragdocs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 RAG Documentation MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 RAG Documentation MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.