Delete a memory from Exocortex by ID. Use when information is outdated or incorrect.
AI agents call memory_forget to permanently remove resources in Exocortex — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (memories) from persistent storage without the ability to undo the operation. Although the data is personal/local rather than production-critical, the irreversible nature of deletion and potential for an AI agent to misuse this against the user's intent (e.g., deleting important context memories needed for task completion) warrants the Destructive category and high severity.
From the tool's definition Tool name 'memory_forget' combined with description 'Delete a memory from Exocortex by ID' explicitly performs irreversible deletion of stored data.
Attacks that exploit this kind of access
Delete a memory from Exocortex by ID. Use when information is outdated or incorrect. It is categorised as a Destructive tool in the Exocortex MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_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 Exocortex. Nothing to install.
memory_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 memory_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 memory_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.
memory_forget is provided by the Exocortex MCP server (shawnhack/exocortex). 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 →