Permanently forget (tombstone) a memory. Args: rid: The memory ID to forget. Returns whether the memory was found and forgotten.
AI agents call memory_forget to permanently remove resources in Yantrikdb — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes stored memories by permanently deleting or marking them for deletion. An AI agent could maliciously forget critical memories, disrupt cognitive continuity, or erase audit trails. While the blast radius depends on what memories exist in the system, the permanent and irreversible nature of the operation classifies it as Destructive rather than Write.
From the tool's definition Tool name 'memory_forget' and description states 'Permanently forget (tombstone) a memory' — the use of 'permanently' and 'tombstone' (a delete marker pattern) indicates irreversible data removal.
Documented attack patterns abuse exactly the kind of access memory_forget gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yantrikdb, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_forget:
{
"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.
Free to start. No card required.
Permanently forget (tombstone) a memory. Args: rid: The memory ID to forget. Returns whether the memory was found and forgotten. It is categorised as a Destructive tool in the Yantrikdb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yantrikdb 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 Yantrikdb. Nothing to install.
memory_forget 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 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.
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.
memory_forget is provided by the Yantrikdb MCP server (yantrikos/yantrikdb-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Yantrikdb tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Yantrikdb tools catalogued and risk-classified — across an index of 42,500+ MCP servers.