AI agents use write_scene_update 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 or modifies data (a 'scene' in the memory engine context) in a reversible manner. It is not destructive because replacement implies the data can be recovered or reverted through other operations. It does not execute code or trigger external side effects. The 'replace' operation is characteristic of Write category tools.
From the tool's definition Tool name 'write_scene_update' and description 'Replace a scene' indicate modification of existing data. The verb 'replace' shows reversible data alteration rather than deletion or irreversible destruction.
Documented attack patterns abuse exactly the kind of access write_scene_update 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_scene_update:
{
"version": "1",
"default": "deny",
"tools": {
"write_scene_update": {
"limits": [
{
"counter": "write_scene_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_scene_update 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.
Replace a scene\. 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_scene_update: 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_scene_update 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_scene_update 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_scene_update. 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_scene_update 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.