memory_forget
AI agents call memory_forget to permanently remove resources in Eve Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'memory_forget' implies irreversible removal of stored memory entries from the shared memory service. In a system where 'All agents share one memory, preferences and rules,' deleting memories could have broad impact across all agents and AI tools. The lack of description lowers confidence slightly, but 'forget' in memory systems universally means deletion/erasure rather than a reversible operation.
From the tool's definition Tool name 'memory_forget' strongly implies permanent deletion or removal of memory data. The description is empty, providing no additional context.
Attacks that exploit this kind of access
memory_forget. It is categorised as a Destructive tool in the Eve Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eve Memory MCP server in PolicyLayer and add a rule for memory_forget: 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 Eve Memory. Nothing to install.
memory_forget 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_forget 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_forget. 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_forget is provided by the Eve Memory MCP server (sherifkozman/eve-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 →