overstory_merge_queue
Read the Overstory merge queue — pending merges, completed merges,
This record as markdown: /tools/io-github-homenshum-nodebench/overstory-merge-queue.md
What overstory_merge_queue does on Nodebench
AI agents call overstory_merge_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 overstory_merge_queue is rated Low
The tool explicitly reads/retrieves the merge queue state (pending and completed merges). This is a read-only operation with no side effects. Low severity since it only exposes queue status information.
From the tool's definition 'Read the Overstory merge queue — pending merges, completed merges'
Attacks that exploit this kind of access
The rule that runs overstory_merge_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 overstory_merge_queue, this is the rule to start with:
overstory_merge_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 overstory_merge_queue call is checked against it from then on.
Questions about overstory_merge_queue
Read the Overstory merge queue — pending merges, completed merges,. 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 overstory_merge_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.
overstory_merge_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 overstory_merge_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 overstory_merge_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.
overstory_merge_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