nb_review_pending_approvals

Review approval-gated receipts waiting for a human decision.

SERVERNodebench SOURCEnodebench-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about nb_review_pending_approvals

What does the nb_review_pending_approvals tool do? +

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.

How do I enforce a policy on nb_review_pending_approvals? +

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.

What risk level is nb_review_pending_approvals? +

nb_review_pending_approvals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nb_review_pending_approvals? +

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.

How do I block nb_review_pending_approvals completely? +

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.

What MCP server provides nb_review_pending_approvals? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.