getEvolutionDashboard
Get the evolution dashboard: latest canary, pending routing recommendations, recent comparisons, and error summary.
This record as markdown: /tools/io-github-homenshum-nodebench/getevolutiondashboard.md
What getEvolutionDashboard does on Nodebench
AI agents call getEvolutionDashboard 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 getEvolutionDashboard is rated Low
This tool retrieves and queries dashboard data for monitoring/observability purposes. There are no side effects—it does not modify state, execute code, delete data, or commit financial transactions. It is a straightforward Read operation with minimal risk if misused by an AI agent, as the worst case is retrieving sensitive monitoring information that could inform subsequent actions.
From the tool's definition Tool name 'getEvolutionDashboard' and description 'Get the evolution dashboard: latest canary, pending routing recommendations, recent comparisons, and error summary' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs getEvolutionDashboard 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 getEvolutionDashboard, this is the rule to start with:
getEvolutionDashboard 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 getEvolutionDashboard call is checked against it from then on.
Questions about getEvolutionDashboard
Get the evolution dashboard: latest canary, pending routing recommendations, recent comparisons, and error summary. 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 getEvolutionDashboard: 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.
getEvolutionDashboard 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 getEvolutionDashboard 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 getEvolutionDashboard. 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.
getEvolutionDashboard 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