list_eval_runs

List recent eval runs with their aggregate scores. Use this to track quality over time and detect drift.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/list-eval-runs.md

WHAT IT DOES

What list_eval_runs does on Nodebench

AI agents call list_eval_runs 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.

RISK

Why list_eval_runs is rated Low

This tool queries and retrieves historical evaluation run data and metrics. It has no capability to modify, delete, or trigger external operations. The purpose is passive monitoring and tracking of quality metrics over time. This is a straightforward Read operation with minimal risk.

From the tool's definition Tool name 'list_eval_runs' and description 'List recent eval runs with their aggregate scores' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_eval_runs 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 list_eval_runs, this is the rule to start with:

list_eval_runs Allowed

list_eval_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_eval_runs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every list_eval_runs call is checked against it from then on.

FAQ

Questions about list_eval_runs

What does the list_eval_runs tool do? +

List recent eval runs with their aggregate scores. Use this to track quality over time and detect drift. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_eval_runs? +

Register the Nodebench MCP server in PolicyLayer and add a rule for list_eval_runs: 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.

What risk level is list_eval_runs? +

list_eval_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_eval_runs? +

Yes. Add a rate_limit block to the list_eval_runs 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.

How do I block list_eval_runs completely? +

Set action: deny in the PolicyLayer policy for list_eval_runs. 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.

What MCP server provides list_eval_runs? +

list_eval_runs 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →