get_forecast_track_record
Get aggregate Brier scores, calibration summary, and track record statistics across all resolved forecasts.
This record as markdown: /tools/io-github-homenshum-nodebench/get-forecast-track-record.md
What get_forecast_track_record does on Nodebench
AI agents call get_forecast_track_record 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 get_forecast_track_record is rated Low
This tool queries historical forecast performance data and returns read-only statistics. No side effects occur—it aggregates and summarizes resolved forecasts without creating, modifying, deleting, or executing any operations. The informational nature of the output and passive retrieval pattern classify it as a Read operation with low severity.
From the tool's definition Tool retrieves aggregate Brier scores, calibration summary, and track record statistics; uses 'get_' prefix indicating data retrieval; no modification, deletion, or execution of external systems
Attacks that exploit this kind of access
The rule that runs get_forecast_track_record 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 get_forecast_track_record, this is the rule to start with:
get_forecast_track_record 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 get_forecast_track_record call is checked against it from then on.
Questions about get_forecast_track_record
Get aggregate Brier scores, calibration summary, and track record statistics across all resolved forecasts. 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 get_forecast_track_record: 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.
get_forecast_track_record 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 get_forecast_track_record 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 get_forecast_track_record. 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.
get_forecast_track_record 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