get_benchmark_report
Get the full detailed report for a specific benchmark batch by batchId.
This record as markdown: /tools/io-github-homenshum-nodebench/get-benchmark-report.md
What get_benchmark_report does on Nodebench
AI agents call get_benchmark_report 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 get_benchmark_report is rated Low
This tool retrieves and returns data (a benchmark report) based on a provided identifier. It performs a query/fetch operation without modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could retrieve reports it shouldn't have access to, but this is a confidentiality concern rather than a destructive or operational risk. Classified as Read with low severity.
From the tool's definition The tool description states 'Get the full detailed report for a specific benchmark batch by batchId.' The verb 'Get' and the read-only nature of retrieving an existing benchmark report indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_benchmark_report 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 get_benchmark_report, this is the rule to start with:
get_benchmark_report 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 get_benchmark_report call is checked against it from then on.
Questions about get_benchmark_report
Get the full detailed report for a specific benchmark batch by batchId. 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 get_benchmark_report: 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.
get_benchmark_report 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 get_benchmark_report 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 get_benchmark_report. 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.
get_benchmark_report 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