mindmap_forget

Forget a memory. By default this is a soft forget: status→archived, kept only as a searchable one-line trace (recall never hard-fails). Set hard=true to permanently delete the file. Args: id (string), hard (boolean, default false). Returns: confirmation.

Server Mindmap @ravi-labs/mindmap-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What mindmap_forget does on Mindmap

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

Why mindmap_forget needs a policy

Although soft-forget is the default (reversible, thus Write), the tool explicitly provides a hard=true parameter that enables permanent deletion without undo capability. Since the tool DOES support irreversible deletion as an intentional feature, it falls into Destructive category per the rule that judges tools by what they CAN do.

From the tool's definition The tool description explicitly states 'Set hard=true to permanently delete the file.' This is an irreversible deletion operation.

Questions about mindmap_forget

What does the mindmap_forget tool do? +

Forget a memory. By default this is a soft forget: status→archived, kept only as a searchable one-line trace (recall never hard-fails). Set hard=true to permanently delete the file. Args: id (string), hard (boolean, default false). Returns: confirmation. It is categorised as a Destructive tool in the Mindmap 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 mindmap_forget? +

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

What risk level is mindmap_forget? +

mindmap_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 mindmap_forget? +

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

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

mindmap_forget is provided by the Mindmap MCP server (@ravi-labs/mindmap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.