Critical Risk →

aim_memory_forget

Forget memories

How to control aim_memory_forget ↓

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

Critical Risk

Forgetting memories implies irreversible deletion of stored knowledge graph data. Unlike 'remove_facts' which may target specific facts, 'forget' suggests wholesale removal of memories, which cannot be undone. This could cause significant loss of persistent user context that Claude relies on across chats, making it high severity.

From the tool's definition 'Forget memories' — the tool is designed to remove/delete stored memory data

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

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

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

aim_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 Mcp Knowledge Graph — 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.

Go deeper

What does the aim_memory_forget tool do? +

Forget memories. It is categorised as a Destructive tool in the Mcp Knowledge Graph 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 aim_memory_forget? +

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

What risk level is aim_memory_forget? +

aim_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 aim_memory_forget? +

Yes. Add a rate_limit block to the aim_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 aim_memory_forget completely? +

Set action: deny in the PolicyLayer policy for aim_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 aim_memory_forget? +

aim_memory_forget is provided by the Mcp Knowledge Graph MCP server (shaneholloman/mcp-knowledge-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Knowledge Graph tool call.

Deterministic rules across all 10 Mcp Knowledge Graph tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Mcp Knowledge Graph tools catalogued and risk-classified — across an index of 42,500+ 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.