nb_review_pending_approvals
Review approval-gated receipts waiting for a human decision.
This record as markdown: /tools/io-github-homenshum-nodebench/nb-review-pending-approvals.md
What nb_review_pending_approvals does on Nodebench
AI agents call nb_review_pending_approvals 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 nb_review_pending_approvals is rated Low
The tool retrieves data about pending approvals for human review. While it accesses potentially sensitive financial approval information (receipts), it performs no write, destructive, or execute operations. The 'approval-gated' context suggests these are sensitive items, warranting medium severity despite Read category, as misuse could expose confidential receipt/financial data to an AI agent.
From the tool's definition Tool name contains 'review' and description states 'Review approval-gated receipts waiting for a human decision' — indicates querying/retrieving pending approval records for inspection, not modifying them.
Attacks that exploit this kind of access
The rule that runs nb_review_pending_approvals 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_review_pending_approvals, this is the rule to start with:
nb_review_pending_approvals 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 nb_review_pending_approvals call is checked against it from then on.
Questions about nb_review_pending_approvals
Review approval-gated receipts waiting for a human decision. 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 nb_review_pending_approvals: 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_review_pending_approvals 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 nb_review_pending_approvals 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_review_pending_approvals. 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_review_pending_approvals 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