decide_re_update
Decide whether to update existing instructions or create new files. Implements
This record as markdown: /tools/io-github-homenshum-nodebench/decide-re-update.md
What decide_re_update does on Nodebench
AI agents use decide_re_update 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 decide_re_update is rated Medium
The tool modifies existing instructions or creates new files, which are reversible write operations. The incomplete description ('Implements' with no follow-up) slightly reduces confidence, but the core action of updating instructions and creating files clearly falls into the Write category. Severity is medium because unintended updates to instructions could affect downstream processes, but effects are reversible.
From the tool's definition Tool name 'decide_re_update' and description 'update existing instructions or create new files' indicate modification of files/instructions (write operation).
Attacks that exploit this kind of access
The rule that runs decide_re_update 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 decide_re_update, this is the rule to start with:
decide_re_update 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 decide_re_update call is checked against it from then on.
Questions about decide_re_update
Decide whether to update existing instructions or create new files. Implements. 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 decide_re_update: 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.
decide_re_update 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 decide_re_update 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 decide_re_update. 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.
decide_re_update 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