Low Risk

write_project_get

Get full project state: metadata, all characters, scene count, total word count, and the 5 most recent scenes. Use to orient yourself when resuming work.

How to control write_project_get ↓

What write_project_get does on Celiums Memory

AI agents call write_project_get 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.

Low Risk

Why write_project_get needs a policy

The tool retrieves and returns existing project data (metadata, characters, scene count, word count, recent scenes) with no modifications. Pure read/query operation with no side effects.

From the tool's definition "Get full project state: metadata, all characters, scene count, total word count, and the 5 most recent scenes"

Documented attack patterns abuse exactly the kind of access write_project_get gives an agent:

How to control write_project_get

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_get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "write_project_get": {}
  }
}

write_project_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Celiums Memory — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about write_project_get

What does the write_project_get tool do? +

Get full project state: metadata, all characters, scene count, total word count, and the 5 most recent scenes. Use to orient yourself when resuming work. It is categorised as a Read tool in the Celiums Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on write_project_get? +

Register the Celiums Memory MCP server in PolicyLayer and add a rule for write_project_get: 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.

What risk level is write_project_get? +

write_project_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit write_project_get? +

Yes. Add a rate_limit block to the write_project_get 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.

How do I block write_project_get completely? +

Set action: deny in the PolicyLayer policy for write_project_get. 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.

What MCP server provides write_project_get? +

write_project_get 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.

Enforce policy on every Celiums Memory tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.