Delete a memory with cascade deletion options. Soft delete (soft=true) sets strength to 0
AI agents call forget to permanently remove resources in ThoughtMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes stored memories from the cognitive system. While 'soft delete' technically leaves a record with zero strength, it operationally destroys access to that memory data. Cascade deletion further suggests secondary data removal. This is irreversible and cannot be undone by the user after execution, making it Destructive rather than Write.
From the tool's definition The tool description states 'Delete a memory' and offers 'cascade deletion options,' indicating irreversible removal of data. Even the 'soft delete' option (setting strength to 0) functionally removes the memory from cognitive processing.
Attacks that exploit this kind of access
Delete a memory with cascade deletion options. Soft delete (soft=true) sets strength to 0. It is categorised as a Destructive tool in the ThoughtMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Thought 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 ThoughtMCP. 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 Thought MCP server (keyurgolani/thoughtmcp). 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 →