Delete a memory by ID.
AI agents call delete_memory to permanently remove resources in N3MemoryCore Lite (Working Memory) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes memory records from the working memory store. While the impact is scoped to ephemeral 7-day data (mitigating some blast radius), the deletion is irreversible within that window. An AI agent with access could maliciously erase important conversational context, repair logs, or decision history.
From the tool's definition Tool name is 'delete_memory' with description 'Delete a memory by ID.' The verb 'delete' and the action of removing data by identifier are unambiguous indicators of irreversible data destruction.
Attacks that exploit this kind of access
Delete a memory by ID. It is categorised as a Destructive tool in the N3MemoryCore Lite (Working Memory) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N3MemoryCore Lite (Working Memory) MCP server in PolicyLayer and add a rule for delete_memory: 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 N3MemoryCore Lite (Working Memory). Nothing to install.
delete_memory 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 delete_memory 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 delete_memory. 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.
delete_memory is provided by the N3MemoryCore Lite (Working Memory) MCP server (NeuralNexusNote/n3mcmcp-lite). 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 →