Remove facts from memory. Can target a specific fact, facts older than a date, or facts older than N days.
AI agents call forget to permanently remove resources in Engram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data from the knowledge base without reversibility. Although the blast radius is limited to the user's own fact store (not a shared system), the irreversible nature of deletion and the lack of recovery options places it in the Destructive category rather than Write.
From the tool's definition Tool name 'forget' with description 'Remove facts from memory' — irreversible deletion of stored data. The ability to target 'a specific fact' or facts matching temporal criteria (older than a date, older than N days) confirms targeted or bulk erasure with no…
Attacks that exploit this kind of access
Remove facts from memory. Can target a specific fact, facts older than a date, or facts older than N days. It is categorised as a Destructive tool in the Engram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Engram 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 Engram. Nothing to install.
forget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
forget is provided by the Engram MCP server (reallyartificial/engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →