get_ab_test_report
Generate an A/B test comparison report for static vs dynamic toolset loading. Shows session counts, tool counts, load events, error rates, and per-toolset load frequency. Use after running sessions in both modes to evaluate the impact of dynamic loading.
This record as markdown: /tools/io-github-homenshum-nodebench/get-ab-test-report.md
What get_ab_test_report does on Nodebench
AI agents call get_ab_test_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_ab_test_report is rated Low
This tool retrieves and compiles metrics from completed A/B test sessions (session counts, tool counts, load events, error rates, load frequency). It performs no modifications, deletions, or external operations—it reads test data and generates a comparative report. This is a pure Read operation with minimal risk of misuse by an AI agent.
From the tool's definition Tool description states it 'Generate[s] an A/B test comparison report' and 'Shows session counts, tool counts, load events, error rates, and per-toolset load frequency.' The verb 'Shows' and 'Generate' for a report, combined with 'Use after running sessions'…
Attacks that exploit this kind of access
The rule that runs get_ab_test_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_ab_test_report, this is the rule to start with:
get_ab_test_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_ab_test_report call is checked against it from then on.
Questions about get_ab_test_report
Generate an A/B test comparison report for static vs dynamic toolset loading. Shows session counts, tool counts, load events, error rates, and per-toolset load frequency. Use after running sessions in both modes to evaluate the impact of dynamic loading. 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_ab_test_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_ab_test_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_ab_test_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_ab_test_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_ab_test_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