Creates a new Scrivener project with full binder structure, labels, statuses, and optional initial content. The new project becomes the active project. Use this to scaffold a writing project from an idea: define the manuscript structure as a hierarchy of Folders (acts/parts/chapters) and Text ite...
AI agents use create_project 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 projects and initializes data structures (folders, documents, metadata), which is a write operation that modifies the file system and project state. While reversible (the created project can be deleted), it commits data persistently. It does not execute arbitrary code, delete existing data, or move money, so Write is the appropriate category.
From the tool's definition Tool description states it 'Creates a new Scrivener project' and 'populate synopsis on every item', explicitly performing creation of persistent project data structures with content.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Creates a new Scrivener project with full binder structure, labels, statuses, and optional initial content. The new project becomes the active project. Use this to scaffold a writing project from an idea: define the manuscript structure as a hierarchy of Folders (acts/parts/chapters) and Text items (scenes/documents), populate synopsis on every item (this is the virtual index card shown in Scrivener. 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 create_project: 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.
create_project 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 create_project 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 create_project. 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.
create_project 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 →