getVerificationSummary
Get a summary of verification health across all tracked facts. Returns counts by verdict (VERIFIED, CORROBORATED, UNVERIFIED, CONTRADICTED, OUTDATED, INSUFFICIENT) and overall trust score.
This record as markdown: /tools/io-github-homenshum-nodebench/getverificationsummary.md
What getVerificationSummary does on Nodebench
AI agents call getVerificationSummary 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 getVerificationSummary is rated Low
This tool performs a read-only query operation that returns counts and metrics related to tracked facts and their verification status. It has no side effects, does not modify data, execute code, delete information, or commit financial obligations. The only risk is potential information disclosure if the verification data is sensitive, but that is minimal for a health summary aggregation function.
From the tool's definition getVerificationSummary retrieves a summary of verification health with counts and scores; uses 'Get' prefix and describes retrieval of aggregated status data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs getVerificationSummary 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 getVerificationSummary, this is the rule to start with:
getVerificationSummary 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 getVerificationSummary call is checked against it from then on.
Questions about getVerificationSummary
Get a summary of verification health across all tracked facts. Returns counts by verdict (VERIFIED, CORROBORATED, UNVERIFIED, CONTRADICTED, OUTDATED, INSUFFICIENT) and overall trust score. 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 getVerificationSummary: 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.
getVerificationSummary 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 getVerificationSummary 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 getVerificationSummary. 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.
getVerificationSummary 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