resolve_forecast
Resolve a forecast with an outcome. Auto-computes Brier and log scores for binary forecasts. Ambiguous outcomes are excluded from scoring.
This record as markdown: /tools/io-github-homenshum-nodebench/resolve-forecast.md
What resolve_forecast does on Nodebench
AI agents use resolve_forecast to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why resolve_forecast is rated Medium
The tool creates or updates forecast resolution data by recording outcomes and computing associated metrics (Brier and log scores). This is a reversible modification of data state, fitting the Write category.
From the tool's definition Tool description states 'Resolve a forecast with an outcome' and 'Auto-computes...scores', indicating it modifies forecast records by recording outcomes and computing results. This is a data modification action.
Attacks that exploit this kind of access
The rule that runs resolve_forecast 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 resolve_forecast, this is the rule to start with:
resolve_forecast stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 resolve_forecast call is checked against it from then on.
Questions about resolve_forecast
Resolve a forecast with an outcome. Auto-computes Brier and log scores for binary forecasts. Ambiguous outcomes are excluded from scoring. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for resolve_forecast: 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.
resolve_forecast is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_forecast 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 resolve_forecast. 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.
resolve_forecast 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