nb_open_approval_queue
Open the approval queue for held actions.
This record as markdown: /tools/io-github-homenshum-nodebench/nb-open-approval-queue.md
What nb_open_approval_queue does on Nodebench
AI agents use nb_open_approval_queue to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why nb_open_approval_queue is rated Medium
An AI agent can call nb_open_approval_queue faster than any human can review: one bad instruction and it creates or modifies resources in Nodebench by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs nb_open_approval_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 nb_open_approval_queue, this is the rule to start with:
nb_open_approval_queue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 nb_open_approval_queue call is checked against it from then on.
Questions about nb_open_approval_queue
Open the approval queue for held actions. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for nb_open_approval_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.
nb_open_approval_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nb_open_approval_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 nb_open_approval_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.
nb_open_approval_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