Delete memories by explicit selector. Requires a reason and defaults to soft delete.
AI agents call memory.delete to permanently remove resources in Lore Context — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (memories) from an AI agent's context store. Even though soft-delete is mentioned as default, the tool's primary function is destructive removal of information that an agent relies on. Misuse could erase critical context, evidence, or audit trails, preventing recovery of past decisions or agent state.
From the tool's definition Tool name 'memory.delete' combined with description 'Delete memories by explicit selector' explicitly performs deletion. The phrase 'defaults to soft delete' indicates reversibility is optional, implying hard-delete capability exists or could be enabled.
Attacks that exploit this kind of access
Delete memories by explicit selector. Requires a reason and defaults to soft delete. It is categorised as a Destructive tool in the Lore Context MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lore Context MCP server in PolicyLayer and add a rule for memory.delete: 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 Lore Context. Nothing to install.
memory.delete 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.delete 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.delete. 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.delete is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →