This record as markdown: /tools/io-github-homenshum-nodebench/update-forecast-probability.md
What update_forecast_probability does on Nodebench
AI agents use update_forecast_probability 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 update_forecast_probability is rated Medium
This tool modifies forecast data (probability values) in a reversible manner. It is not destructive since updates can typically be undone or corrected. It is not Read (retrieves data) or Execute (runs arbitrary code/commands). The medium severity reflects that incorrect probability updates could propagate through decision-making systems, but the impact depends on how forecasts are used downstream.
From the tool's definition Tool name 'update_forecast_probability' combined with description 'Update a forecast' indicates modification of existing data. The verb 'update' is characteristic of Write operations that reversibly change data.
Attacks that exploit this kind of access
The rule that runs update_forecast_probability 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 update_forecast_probability, this is the rule to start with:
update_forecast_probability 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 update_forecast_probability call is checked against it from then on.
Questions about update_forecast_probability
Update 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 update_forecast_probability: 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.
update_forecast_probability 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 update_forecast_probability 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 update_forecast_probability. 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.
update_forecast_probability 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