Critical Risk →

memory_forget

memory_forget

How to control memory_forget ↓

What memory_forget does on Locus

AI agents call memory_forget to permanently remove resources in Locus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why memory_forget needs a policy

The name 'memory_forget' strongly implies irreversible removal of stored memory/context data. Combined with the sibling tool 'memory_purge' confirming destructive operations exist on this server, and the server's purpose of storing persistent project context and conversation recall, forgetting likely means permanently deleting stored memories.

From the tool's definition Tool name 'memory_forget' on a server described as 'Local persistent memory for AI coding tools. Stores project context and conversation recall locally via MCP.' Sibling tools include 'memory_purge', suggesting destructive operations exist in this toolset.

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

How to control memory_forget

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "memory_forget"
  ]
}

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

  1. Create a free account and register Locus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_forget

What does the memory_forget tool do? +

memory_forget. It is categorised as a Destructive tool in the Locus 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 memory_forget? +

Register the Locus 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 Locus. Nothing to install.

What risk level is memory_forget? +

memory_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 memory_forget? +

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.

How do I block memory_forget completely? +

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.

What MCP server provides memory_forget? +

memory_forget is provided by the Locus MCP server (magnifico4625/locus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Locus tool call.

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

Free to start. No card required.

17 Locus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.