Elimina una memoria por su ID.
AI agents call delete_memory to permanently remove resources in Engram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes individual memory records from the persistent storage system. Deletion is irreversible and cannot be undone. Given that the server stores critical long-term context for AI agents, deleting memories could disrupt agent operations and eliminate historical records. While not directly financial, the high consequence to data integrity and agent functionality justifies 'high' severity.
From the tool's definition delete_memory with description 'Elimina una memoria por su ID' (Deletes a memory by its ID) - irreversibly removes stored data from the SQLite database without recovery option mentioned.
Attacks that exploit this kind of access
Elimina una memoria por su ID. It is categorised as a Destructive tool in the Engram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Engram 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 Engram. 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 Engram MCP server (jacksini/engram-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 →