Store a memory with full security gating (RBAC memory:write + AAL R2 + audit).
AI agents use memory_remember_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 creates or modifies persistent memory data in the cognitive engine. While the security gating (RBAC memory:write permission, AAL R2 authentication, audit logging) reduces risk and prevents unauthorized access, the core function remains a reversible data modification operation. The blast radius is limited to memory storage within the agent's context, making it medium severity rather than high.
From the tool's definition Tool name contains 'remember' and description states 'Store a memory', which are write operations that create or modify data. The security controls (RBAC, AAL R2, audit) mitigate but do not eliminate the write capability.
Documented attack patterns abuse exactly the kind of access memory_remember_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_remember_secure:
{
"version": "1",
"default": "deny",
"tools": {
"memory_remember_secure": {
"limits": [
{
"counter": "memory_remember_secure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memory_remember_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.
Store a memory with full security gating (RBAC memory:write + AAL R2 + audit). 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_remember_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_remember_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_remember_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_remember_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_remember_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.