runway_check
Basic runway check that translates cash and burn into months remaining and flags risk.
This record as markdown: /tools/io-github-homenshum-nodebench/runway-check.md
What runway_check does on Nodebench
AI agents call runway_check 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 runway_check is rated Low
The tool reads/queries financial data (cash position, burn rate) and performs computational analysis to produce a report with risk flags. This is a read-only analytical operation—it retrieves and processes information without executing payments, modifying financial records, or triggering irreversible actions. The 'flags risk' output suggests diagnostic warnings rather than financial operations.
From the tool's definition Tool performs calculation and analysis of financial metrics ('translates cash and burn into months remaining') with 'flags risk' indicating diagnostic output. No modification, deletion, or financial transaction execution described.
Attacks that exploit this kind of access
The rule that runs runway_check 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 runway_check, this is the rule to start with:
runway_check 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 runway_check call is checked against it from then on.
Questions about runway_check
Basic runway check that translates cash and burn into months remaining and flags risk. 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 runway_check: 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.
runway_check 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 runway_check 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 runway_check. 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.
runway_check 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