Admin/owner only (§4.5). Retire or supersede a journal entry WITHOUT deleting it — inserts into journal_supersession so recall/arc/introspect default-exclude the original while the SHA-256 hash chain stays intact (journal_verify_chain remains valid). Succession: pass original_entry_id + new_entry...
AI agents use journal_supersede 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.
Although journal_supersede does not delete data (ruling out Destructive), it performs a consequential write operation that modifies the retrieval and interpretation of persistent user memory.
From the tool's definition Tool 'journal_supersede' modifies memory state by inserting into journal_supersession, marking entries as retired/superseded, and altering default recall/arc/introspect behavior.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access journal_supersede 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 journal_supersede:
{
"version": "1",
"default": "deny",
"tools": {
"journal_supersede": {
"limits": [
{
"counter": "journal_supersede_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}journal_supersede 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.
Admin/owner only (§4.5). Retire or supersede a journal entry WITHOUT deleting it — inserts into journal_supersession so recall/arc/introspect default-exclude the original while the SHA-256 hash chain stays intact (journal_verify_chain remains valid). Succession: pass original_entry_id + new_entry_id + relation (superseded|nuanced|reaffirmed). Retraction of a junk/smoke entry with no successor: relation=. 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 journal_supersede: 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.
journal_supersede 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 journal_supersede 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 journal_supersede. 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.
journal_supersede 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.