updatePlanStep
Update the status or notes of a specific step in a task plan
This record as markdown: /tools/io-github-homenshum-nodebench/updateplanstep.md
What updatePlanStep does on Nodebench
AI agents use updatePlanStep 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 updatePlanStep is rated Medium
This tool modifies task plan metadata (status and notes) without deleting or irreversibly destroying data. It does not execute arbitrary code, move money, or trigger destructive operations. The blast radius is medium because incorrect updates to task steps could disrupt workflows or cause confusion, but changes can be reverted by updating again.
From the tool's definition Tool description states 'Update the status or notes' which indicates modification of existing data (a task plan step). The verb 'update' and the modifiable fields (status, notes) confirm reversible data modification.
Attacks that exploit this kind of access
The rule that runs updatePlanStep 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 updatePlanStep, this is the rule to start with:
updatePlanStep 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 updatePlanStep call is checked against it from then on.
Questions about updatePlanStep
Update the status or notes of a specific step in a task plan. 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 updatePlanStep: 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.
updatePlanStep 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 updatePlanStep 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 updatePlanStep. 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.
updatePlanStep 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