forget_source
AI agents call forget_source to permanently remove resources in MemoryMesh — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'forget_source' in the context of a memory/indexing server strongly implies permanently removing a source (document, file, or data index) from the system. This is consistent with the sibling tool 'forget_memory', suggesting a pattern of irreversible deletion operations. Removing an indexed source would be difficult or impossible to undo without re-indexing, making this Destructive.
From the tool's definition Tool name 'forget_source' combined with server context of indexing personal files and sources; 'forget' strongly implies removal/deletion of an indexed source from the memory system.
Attacks that exploit this kind of access
forget_source. It is categorised as a Destructive tool in the MemoryMesh MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MemoryMesh MCP server in PolicyLayer and add a rule for forget_source: 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 MemoryMesh. Nothing to install.
forget_source 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 forget_source 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 forget_source. 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.
forget_source is provided by the MemoryMesh MCP server (kilhubprojects/memory-mesh). 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 →