evidence_gap_scan
List missing evidence classes and materials for diligence readiness.
This record as markdown: /tools/io-github-homenshum-nodebench/evidence-gap-scan.md
What evidence_gap_scan does on Nodebench
AI agents call evidence_gap_scan 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 evidence_gap_scan is rated Low
This tool performs a scan to list or report on missing evidence, which is a read-only operation. It retrieves or reports status information relevant to diligence preparation. No data is modified, executed, destroyed, or financial commitments are made. The blast radius of misuse is minimal—an agent could generate inaccurate reports of missing evidence, but cannot cause system damage or data loss.
From the tool's definition Tool name 'evidence_gap_scan' and description 'List missing evidence classes and materials for diligence readiness' indicate a query/retrieval operation that identifies gaps in evidence documentation without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs evidence_gap_scan 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 evidence_gap_scan, this is the rule to start with:
evidence_gap_scan 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 evidence_gap_scan call is checked against it from then on.
Questions about evidence_gap_scan
List missing evidence classes and materials for diligence readiness. 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 evidence_gap_scan: 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.
evidence_gap_scan 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 evidence_gap_scan 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 evidence_gap_scan. 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.
evidence_gap_scan 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