Permanently delete a memory from all ManasDB databases using its contentId. The contentId is returned when memorize is called. Use recall first to find the contentId of what you want to forget.
AI agents call forget to permanently remove resources in Manasdb — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (memories) from persistent storage across multiple databases. While the blast radius is limited to the AI agent's own stored memories rather than shared critical systems, permanent deletion without recovery options meets the Destructive category definition.
From the tool's definition 'Permanently delete a memory' and 'delete a memory from all ManasDB databases' indicate irreversible deletion of data.
Attacks that exploit this kind of access
Permanently delete a memory from all ManasDB databases using its contentId. The contentId is returned when memorize is called. Use recall first to find the contentId of what you want to forget. It is categorised as a Destructive tool in the Manasdb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Manasdb 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 Manasdb. 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 Manasdb MCP server (manasdb/mcp-server). 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 →