Critical Risk →

forget

Delete specific memories by ID. Requires explicit IDs — will not bulk delete.

How to control forget ↓

What forget does on Celiums Memory

AI agents call forget to permanently remove resources in Celiums Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why forget needs a policy

This tool deletes data that cannot be recovered. Although it requires explicit IDs (reducing accidental bulk damage), deletion of memories is an irreversible operation with high blast radius if an AI agent misuses it to remove important user context, project state, or personal information. Destructive is the correct category per the severity hierarchy.

From the tool's definition Tool name is 'forget' with description 'Delete specific memories by ID.' The verb 'Delete' combined with permanent removal of user memories—a core asset of a cognitive memory engine—makes this irreversibly destructive.

Documented attack patterns abuse exactly the kind of access forget gives an agent:

How to control forget

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 forget:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "forget"
  ]
}

forget disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Celiums Memory — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about forget

What does the forget tool do? +

Delete specific memories by ID. Requires explicit IDs — will not bulk delete. It is categorised as a Destructive tool in the Celiums Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on forget? +

Register the Celiums Memory MCP server in PolicyLayer and add a rule for forget: 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.

What risk level is forget? +

forget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit forget? +

Yes. Add a rate_limit block to the forget 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.

How do I block forget completely? +

Set action: deny in the PolicyLayer policy for forget. 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.

What MCP server provides forget? +

forget 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.

Enforce policy on every Celiums Memory tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.