getMissionDashboard
Get the mission control dashboard: active missions, judging queue, sniff checks, and recent completions.
This record as markdown: /tools/io-github-homenshum-nodebench/getmissiondashboard.md
What getMissionDashboard does on Nodebench
AI agents call getMissionDashboard 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 getMissionDashboard is rated Low
This tool retrieves and displays dashboard information without creating, modifying, or deleting any data. It has no side effects and poses minimal security risk even if misused by an AI agent, as it only exposes existing dashboard state.
From the tool's definition Tool name 'getMissionDashboard' and description 'Get the mission control dashboard' clearly indicates data retrieval with no mutation. The dashboard presents read-only summaries of 'active missions, judging queue, sniff checks, and recent completions'.
Attacks that exploit this kind of access
The rule that runs getMissionDashboard 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 getMissionDashboard, this is the rule to start with:
getMissionDashboard 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 getMissionDashboard call is checked against it from then on.
Questions about getMissionDashboard
Get the mission control dashboard: active missions, judging queue, sniff checks, and recent completions. 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 getMissionDashboard: 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.
getMissionDashboard 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 getMissionDashboard 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 getMissionDashboard. 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.
getMissionDashboard 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