Adds a new document or folder to the binder of the active project. Will fail with a clear error if Scrivener has the project open — close Scrivener first. Use this to extend the structure of an existing project: add a new scene to a chapter, a new chapter to an act, a new research note, or a whol...
AI agents use add_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 creates new documents and folders within a Scrivener project, which is a reversible write operation. While it modifies project state, the changes can be undone (documents can be deleted). It does not execute arbitrary code, delete data irreversibly, move money, or merely read data. Write is the appropriate category as it creates and persists new data structures within the project.
From the tool's definition Tool description states it 'Adds a new document or folder to the binder' and 'extend[s] the structure of an existing project', creating new items that are returned. The tool modifies project structure by adding content reversibly.
Attacks that exploit this kind of access
Adds a new document or folder to the binder of the active project. Will fail with a clear error if Scrivener has the project open — close Scrivener first. Use this to extend the structure of an existing project: add a new scene to a chapter, a new chapter to an act, a new research note, or a whole new folder. Always populate synopsis — it is the index card text that makes the corkboard and outliner useful for structural reasoning. If parentUuid is omitted, the item is appended to the top level of the Manuscript folder. Returns the new item. 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 add_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.
add_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 add_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 add_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.
add_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 →