open_operating_dashboard
Start the Operating Dashboard — shows trajectory scores, event ledger, important changes, path replay, time rollups, packet readiness, and recent actions. The ambient intelligence surface for your business. All from local SQLite.
This record as markdown: /tools/io-github-homenshum-nodebench/open-operating-dashboard.md
What open_operating_dashboard does on Nodebench
AI agents call open_operating_dashboard 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 open_operating_dashboard is rated Low
The tool opens a dashboard that displays various metrics and data from a local SQLite database. It reads and presents information (scores, ledger, changes, actions) without creating, modifying, or deleting data. The word 'Start' refers to launching a UI view, not executing destructive or write operations. Low severity as it only surfaces local read-only analytics.
From the tool's definition 'Start the Operating Dashboard — shows trajectory scores, event ledger, important changes, path replay, time rollups, packet readiness, and recent actions' — purely displays/reads data from local SQLite
Attacks that exploit this kind of access
The rule that runs open_operating_dashboard 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 open_operating_dashboard, this is the rule to start with:
open_operating_dashboard 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 open_operating_dashboard call is checked against it from then on.
Questions about open_operating_dashboard
Start the Operating Dashboard — shows trajectory scores, event ledger, important changes, path replay, time rollups, packet readiness, and recent actions. The ambient intelligence surface for your business. All from local SQLite. 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 open_operating_dashboard: 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.
open_operating_dashboard 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 open_operating_dashboard 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 open_operating_dashboard. 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.
open_operating_dashboard 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