updateDocument
Update document fields: title, content, icon, visibility, favorite status.
This record as markdown: /tools/io-github-homenshum-nodebench/updatedocument.md
What updateDocument does on Nodebench
AI agents use updateDocument 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 updateDocument is rated Medium
This tool creates or modifies data reversibly by updating document metadata and content. It does not delete data (which would be Destructive), execute code (Execute), or move money (Financial). The moderate severity reflects that document modifications could affect visibility/access or overwrite content, but changes are typically reversible through subsequent updates.
From the tool's definition Tool description explicitly states 'Update document fields: title, content, icon, visibility, favorite status.' The verb 'Update' and the enumerated modifiable fields indicate reversible modifications to existing documents.
Attacks that exploit this kind of access
The rule that runs updateDocument 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 updateDocument, this is the rule to start with:
updateDocument 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 updateDocument call is checked against it from then on.
Questions about updateDocument
Update document fields: title, content, icon, visibility, favorite status. 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 updateDocument: 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.
updateDocument 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 updateDocument 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 updateDocument. 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.
updateDocument 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