upsert_durable_object
Register or update a durable local object so views, tools, workflows, runs, artifacts, and outcomes share one replayable identity spine.
This record as markdown: /tools/io-github-homenshum-nodebench/upsert-durable-object.md
What upsert_durable_object does on Nodebench
AI agents use upsert_durable_object 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 upsert_durable_object is rated Medium
The tool performs a reversible create-or-update operation on a durable object used across multiple subsystems. This is Write-category (not Execute, since it doesn't run arbitrary code; not Destructive, since upsert is reversible).
From the tool's definition Tool name contains 'upsert' (create/update operation); description states 'Register or update' a durable object, and 'share one replayable identity spine' indicates modification of shared state affecting multiple system components (views, tools, workflows,…
Attacks that exploit this kind of access
The rule that runs upsert_durable_object 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 upsert_durable_object, this is the rule to start with:
upsert_durable_object 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 upsert_durable_object call is checked against it from then on.
Questions about upsert_durable_object
Register or update a durable local object so views, tools, workflows, runs, artifacts, and outcomes share one replayable identity spine. 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 upsert_durable_object: 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.
upsert_durable_object 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 upsert_durable_object 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 upsert_durable_object. 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.
upsert_durable_object 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