forget

THE RISK

Critical Risk

Why forget needs a policy

This tool explicitly deletes memories, which is an irreversible destructive operation. Misuse by an AI agent could result in permanent loss of stored context/memories across sessions, which is the core value of this memory system. The blast radius is high since deleted memories cannot be recovered.

From the tool's definition "Request deletion of specific memories from a space"

Documented attack patterns abuse exactly the kind of access forget gives an agent:

POLICY

How to control forget

PolicyLayer is an MCP gateway — it sits between your AI agents and Evermemos, and nothing reaches the server without passing your rules. This is the rule we recommend for forget:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "forget"
  ]
}

forget disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Evermemos — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Evermemos tools

Write remember Store information in long-term memory within a specific space. Read briefing Get a structured context briefing for a memory space. Read fetch_history Page through historical memories in a space by memory_type. Read list_spaces List MCP-visible memory spaces that this server can route and recover. Read recall Search for relevant memories in one or more spaces. Read request_status Check the async processing status for a prior remember request.

All 7 Evermemos tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Evermemos → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about forget

What does the forget tool do? +

Request deletion of specific memories from a space. It is categorised as a Destructive tool in the Evermemos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on forget? +

Register the Evermemos MCP server in PolicyLayer and add a rule for 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 Evermemos. Nothing to install.

What risk level is forget? +

forget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit forget? +

Yes. Add a rate_limit block to the 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.

How do I block forget completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides forget? +

forget is provided by the Evermemos MCP server (tt-a1i/evermemos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Evermemos tool call.

Start from Evermemos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →