query_research_queue
View the research task queue from the Convex platform. Shows active and pending research topics with priorities, entities, personas, and quality scores.
This record as markdown: /tools/io-github-homenshum-nodebench/query-research-queue.md
What query_research_queue does on Nodebench
AI agents call query_research_queue to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why query_research_queue is rated Low
This tool performs a read-only operation querying data from a Convex platform. It retrieves information about research tasks (priorities, entities, personas, quality scores) but does not create, modify, delete, or execute any actions. The verb 'View' and 'Shows' confirm passive data retrieval. Low severity because misuse would only expose research queue information without side effects.
From the tool's definition Tool description states it "View[s] the research task queue" and "Shows active and pending research topics" — these are retrieval/query operations with no modification or execution implied.
Attacks that exploit this kind of access
The rule that runs query_research_queue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_research_queue, this is the rule to start with:
query_research_queue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every query_research_queue call is checked against it from then on.
Questions about query_research_queue
View the research task queue from the Convex platform. Shows active and pending research topics with priorities, entities, personas, and quality scores. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for query_research_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 Nodebench. Nothing to install.
query_research_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 query_research_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 query_research_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.
query_research_queue is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue