Delete a memory by ID. Use only when the user explicitly asks to forget something or when a fact is permanently invalid.
AI agents call memory_delete to permanently remove resources in LedgerMem MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes stored memory records. While the data domain is AI context rather than financial or operational systems, deletion operations are categorized as Destructive. An AI agent with access to this tool could maliciously erase important memories, manipulate conversation history, or prevent recall of critical information.
From the tool's definition Tool name is 'memory_delete' and description states 'Delete a memory by ID'. The verb 'delete' is explicitly destructive; the operation removes data irreversibly.
Attacks that exploit this kind of access
Delete a memory by ID. Use only when the user explicitly asks to forget something or when a fact is permanently invalid. It is categorised as a Destructive tool in the LedgerMem MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LedgerMem MCP Server 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 LedgerMem MCP Server. 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 LedgerMem MCP Server MCP server (ledgermem/getmnemo-mcp). 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 →