Create a writing project (novel, screenplay, long-form). Returns a project_id used by all other write_* tools. structureTemplate enables beat tracking against a known structure: three-act | save-the-cat | hero-journey | snowflake | free.
AI agents use write_project_create to create or update resources in Celiums Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Celiums Memory environment.
This tool creates a new data record (writing project) with metadata and returns an identifier. It is purely a write operation that adds a new entry to the system without executing code, deleting data, or causing financial impact. The blast radius of misuse is minimal—a created project can be abandoned or removed. Severity is low because creation of benign metadata poses no significant risk.
From the tool's definition Tool name contains 'write' and 'create'; description states it 'Create[s] a writing project' and 'Returns a project_id'. The action is reversible (projects can be deleted/modified) and creates data structures for organizing writing content.
Documented attack patterns abuse exactly the kind of access write_project_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Celiums Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for write_project_create:
{
"version": "1",
"default": "deny",
"tools": {
"write_project_create": {
"limits": [
{
"counter": "write_project_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_project_create 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.
Free to start. No card required.
Create a writing project (novel, screenplay, long-form). Returns a project_id used by all other write_* tools. structureTemplate enables beat tracking against a known structure: three-act | save-the-cat | hero-journey | snowflake | free. It is categorised as a Write tool in the Celiums Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for write_project_create: 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 Celiums Memory. Nothing to install.
write_project_create 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 write_project_create 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 write_project_create. 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.
write_project_create is provided by the Celiums Memory MCP server (terrizoaguimor/celiums-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Celiums Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Celiums Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.