Patch fields of an existing memory with full security gating (RBAC memory:write
AI agents use memory_update_secure 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 modifies existing memory records by patching fields, which is a reversible write operation. It does not delete data (Destructive), execute code (Execute), or move money (Financial). The 'secure' designation and RBAC gating mitigate blast radius but do not change the fundamental write classification.
From the tool's definition Tool name 'memory_update_secure' combined with description 'Patch fields of an existing memory' indicates modification of data. The phrase 'RBAC memory:write' explicitly confirms write-level access control is required.
Documented attack patterns abuse exactly the kind of access memory_update_secure 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 memory_update_secure:
{
"version": "1",
"default": "deny",
"tools": {
"memory_update_secure": {
"limits": [
{
"counter": "memory_update_secure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memory_update_secure 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.
Patch fields of an existing memory with full security gating (RBAC memory:write. 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 memory_update_secure: 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.
memory_update_secure 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 memory_update_secure 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 memory_update_secure. 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.
memory_update_secure 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.