Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
AI agents call forget to permanently remove resources in Bhagavad Gita — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Memory key to delete |
Parameters from the server's own tool schema.
Although the tool operates on user-controlled memory storage rather than primary application data, it permanently removes information. An AI agent instructed by a malicious prompt could selectively delete legitimate memory records, audit trails, or sensitive data that were previously stored via 'remember', disrupting workflow integrity and potentially hiding evidence of prior operations.
From the tool's definition 'Delete a previously stored memory by key' - the tool irreversibly removes stored data without recovery mechanism. The action cannot be undone, fitting the destructive criteria.
Attacks that exploit this kind of access
Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall. It is categorised as a Destructive tool in the Bhagavad Gita MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
forget accepts 1 parameter: key. Required: key. The full parameter table on this page comes from the server's own tool schema.
Register the Bhagavad Gita MCP server in PolicyLayer and add a rule for 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 Bhagavad Gita. Nothing to install.
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 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 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.
forget is provided by the Bhagavad Gita MCP server (https://gateway.pipeworx.io/bhagavad-gita/mcp). 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 →