AI agents use removeDocumentFromFolder 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.
Removing a document from a folder is a reversible organizational action (the document itself is not deleted, only its association with the folder is changed). This is most accurately classified as a Write operation. Severity is medium because misuse could disorganize document structures, but the document remains intact.
From the tool's definition Remove a document from a folder
Attacks that exploit this kind of access
Remove a document from a folder. 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 removeDocumentFromFolder: 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.
removeDocumentFromFolder 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 removeDocumentFromFolder 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 removeDocumentFromFolder. 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.
removeDocumentFromFolder 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.