Recall memories with full security gating (RBAC memory:read + AAL R1 + audit).
AI agents call memory_recall_secure 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.
This tool retrieves or queries memory data with authentication/authorization protections in place. It performs a read-only operation on stored memories within the cognitive engine. The security gating (RBAC, audit) mitigates misuse risk. No side effects or irreversible actions are indicated.
From the tool's definition Tool name contains 'recall' and description explicitly states 'Recall memories' with security controls (RBAC, AAL, audit). No mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access memory_recall_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_recall_secure:
{
"version": "1",
"default": "deny",
"tools": {
"memory_recall_secure": {}
}
}memory_recall_secure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Recall memories with full security gating (RBAC memory:read + AAL R1 + audit). It is categorised as a Read tool in the Celiums Memory MCP Server, which means it retrieves data without modifying state.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for memory_recall_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_recall_secure is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_recall_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_recall_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_recall_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.