This record as markdown: /tools/io-github-homenshum-nodebench/add-forecast-evidence.md
What add_forecast_evidence does on Nodebench
AI agents use add_forecast_evidence 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 add_forecast_evidence is rated Medium
This tool modifies data reversibly by adding evidence to forecasts—a typical write operation. It does not delete, execute code, move money, or trigger external operations with unpredictable side effects. The 'add' verb and 'evidence' object suggest data augmentation rather than destructive action.
From the tool's definition Tool name 'add_forecast_evidence' and description 'Add evidence to a forecast' indicate the tool creates or modifies forecast-related data by appending evidence to an existing forecast record.
Attacks that exploit this kind of access
The rule that runs add_forecast_evidence 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 add_forecast_evidence, this is the rule to start with:
add_forecast_evidence 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 add_forecast_evidence call is checked against it from then on.
Questions about add_forecast_evidence
Add evidence to a forecast. 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 add_forecast_evidence: 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.
add_forecast_evidence 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 add_forecast_evidence 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 add_forecast_evidence. 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.
add_forecast_evidence 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