getPendingSniffChecks
Get all pending human-in-the-loop sniff checks awaiting review.
This record as markdown: /tools/io-github-homenshum-nodebench/getpendingsniffchecks.md
What getPendingSniffChecks does on Nodebench
AI agents call getPendingSniffChecks 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 getPendingSniffChecks is rated Low
This tool queries a list of pending review items without side effects. It reads data from an existing state (pending checks) and returns it for inspection. No data is created, modified, deleted, or external processes triggered by the tool itself.
From the tool's definition Tool retrieves 'pending human-in-the-loop sniff checks awaiting review' with no indication of modification, deletion, or execution of external operations. The verb 'Get' and passive construction 'awaiting review' indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs getPendingSniffChecks 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 getPendingSniffChecks, this is the rule to start with:
getPendingSniffChecks 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 getPendingSniffChecks call is checked against it from then on.
Questions about getPendingSniffChecks
Get all pending human-in-the-loop sniff checks awaiting review. 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 getPendingSniffChecks: 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.
getPendingSniffChecks 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 getPendingSniffChecks 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 getPendingSniffChecks. 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.
getPendingSniffChecks 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