Export the project as a markdown manuscript. Scenes are emitted in position order, grouped by chapter_id, with POV character and time markers as italic interstitials. Use as a clean preview or to ship into Notion / docx tooling later.
AI agents call write_export to retrieve information from Celiums Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the 'write' prefix in its name, this tool reads/retrieves existing project data and formats it as a markdown manuscript for export. It does not create, modify, or delete data — it assembles scenes in order and emits them. The export is a read-only rendering operation. Severity is low as misuse would only expose project content.
From the tool's definition Export the project as a markdown manuscript... Use as a clean preview or to ship into Notion / docx tooling later.
Documented attack patterns abuse exactly the kind of access write_export 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_export:
{
"version": "1",
"default": "deny",
"tools": {
"write_export": {}
}
}write_export is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export the project as a markdown manuscript. Scenes are emitted in position order, grouped by chapter_id, with POV character and time markers as italic interstitials. Use as a clean preview or to ship into Notion / docx tooling later. It is categorised as a Read tool in the Celiums Memory MCP Server, which means it retrieves data without modifying state.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for write_export: 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_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the write_export 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_export. 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_export 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.