Delete multiple memories in a single batch operation.
AI agents call batch_forget to permanently remove resources in ThoughtMCP — 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 in batch, which cannot be undone. While the blast radius is somewhat contained to the cognitive memory system rather than production data or financial systems, batch deletion operations are inherently destructive and warrant high severity. The batch nature amplifies the risk by allowing deletion of many memories simultaneously without individual confirmation.
From the tool's definition Tool name 'batch_forget' combined with description 'Delete multiple memories in a single batch operation' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete multiple memories in a single batch operation. It is categorised as a Destructive tool in the ThoughtMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Thought MCP server in PolicyLayer and add a rule for batch_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 ThoughtMCP. Nothing to install.
batch_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 batch_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 batch_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.
batch_forget is provided by the Thought MCP server (keyurgolani/thoughtmcp). 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 →