This record as markdown: /tools/io-github-homenshum-nodebench/restoredocument.md
What restoreDocument does on Nodebench
AI agents use restoreDocument 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 restoreDocument is rated Medium
This tool restores archived documents to an active state—a reversible modification of document metadata/status. While it changes system state, it is not destructive (the document still exists and can be re-archived) nor does it delete data. It's classified as Write rather than Execute because the action's effect is straightforward state restoration without arbitrary code execution or external side effects.
From the tool's definition Tool name 'restoreDocument' combined with description 'Restore an archived document and its children' indicates a modification operation that reverses a previous archival action.
Attacks that exploit this kind of access
The rule that runs restoreDocument 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 restoreDocument, this is the rule to start with:
restoreDocument 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 restoreDocument call is checked against it from then on.
Questions about restoreDocument
Restore an archived document and its children. 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 restoreDocument: 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.
restoreDocument 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 restoreDocument 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 restoreDocument. 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.
restoreDocument 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