getLatestDashboard
Get the latest research dashboard snapshot with metrics on deal flow, entity coverage, verification health, and model costs.
This record as markdown: /tools/io-github-homenshum-nodebench/getlatestdashboard.md
What getLatestDashboard does on Nodebench
AI agents call getLatestDashboard 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 getLatestDashboard is rated Low
This tool queries and retrieves existing dashboard metrics without altering any data or triggering external operations. It is a straightforward read operation with no destructive, financial, or execution implications. The low severity reflects minimal risk if misused by an AI agent—at most, it exposes metrics that may already be intended for viewing.
From the tool's definition Tool name and description indicate retrieval of dashboard data: 'Get the latest research dashboard snapshot with metrics on deal flow, entity coverage, verification health, and model costs.' The verb 'Get' and the passive nature of retrieving pre-computed…
Attacks that exploit this kind of access
The rule that runs getLatestDashboard 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 getLatestDashboard, this is the rule to start with:
getLatestDashboard 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 getLatestDashboard call is checked against it from then on.
Questions about getLatestDashboard
Get the latest research dashboard snapshot with metrics on deal flow, entity coverage, verification health, and model costs. 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 getLatestDashboard: 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.
getLatestDashboard 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 getLatestDashboard 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 getLatestDashboard. 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.
getLatestDashboard 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