Moves a binder item to a different parent folder. Will fail with a clear error if Scrivener has the project open — close Scrivener first. Use this to restructure the project: move a scene from one chapter to another, promote a scene to chapter level, reorganise acts, or move a document into the R...
AI agents use move_document to create or update resources in Scrivener — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scrivener environment.
This tool modifies the structure and organization of data within a Scrivener project by changing parent-child relationships in the document hierarchy. This is a reversible structural modification (documents can be moved back), not a deletion or irreversible change. It does not execute arbitrary code or commands, nor does it create side effects beyond reordering.
From the tool's definition The tool description states it 'Moves a binder item to a different parent folder' and enables users to 'restructure the project: move a scene from one chapter to another, promote a scene to chapter level, reorganise acts, or move a document into the Research…
Attacks that exploit this kind of access
Moves a binder item to a different parent folder. Will fail with a clear error if Scrivener has the project open — close Scrivener first. Use this to restructure the project: move a scene from one chapter to another, promote a scene to chapter level, reorganise acts, or move a document into the Research folder. The item retains all its content and metadata; only its position in the hierarchy changes. If newParentUuid is omitted, the item is moved to the top level of the Manuscript folder. Call get_outline first to understand the current structure before reorganising. It is categorised as a Write tool in the Scrivener MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scrivener MCP server in PolicyLayer and add a rule for move_document: 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 Scrivener. Nothing to install.
move_document 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 move_document 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 move_document. 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.
move_document is provided by the Scrivener MCP server (sschmitt-cg/scrivener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →