Delete a memory by id. memory_id MUST be the id returned by search_memory or list_memory—do not use any other value. Use when user asks to forget something or information is outdated.
AI agents call delete_memory to permanently remove resources in Memoryx — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
memory_id | string | Yes | Id from search_memory or list_memory result (required) |
Parameters from the server's own tool schema.
This tool permanently removes stored memories, which cannot be undone. Although the blast radius is limited to personal memory records (not system-critical data), the irreversible nature of deletion and potential loss of important contextual information justifies the Destructive category and medium severity. Confidence is high because the intent is explicit in both name and description.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete a memory by id.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a memory by id. memory_id MUST be the id returned by search_memory or list_memory—do not use any other value. Use when user asks to forget something or information is outdated. It is categorised as a Destructive tool in the Memoryx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_memory accepts 1 parameter: memory_id. Required: memory_id. The full parameter table on this page comes from the server's own tool schema.
Register the Memoryx 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 Memoryx. 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 Memoryx MCP server (@t0ken.ai/memoryx-mcp-server). 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 →