AI agents call deleteMemory to permanently remove resources in ThinkMem — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes entire memory blocks and their contents without possibility of reversal. While the blast radius is limited to the LLM's memory storage rather than external systems, the irreversible destruction of data classifies it as Destructive.
From the tool's definition The tool description states '删除指定的Memory存储块及其包含的所有数据' which translates to 'Delete the specified Memory storage block and all data contained within it.' The term '删除' (delete) combined with 'all data contained within it' indicates irreversible removal.
Documented attack patterns abuse exactly the kind of access deleteMemory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThinkMem, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteMemory:
{
"version": "1",
"default": "deny",
"hide": [
"deleteMemory"
]
}deleteMemory 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.
删除指定的Memory存储块及其包含的所有数据。. It is categorised as a Destructive tool in the ThinkMem MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ThinkMem MCP server in PolicyLayer and add a rule for deleteMemory: 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 ThinkMem. Nothing to install.
deleteMemory 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 deleteMemory 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 deleteMemory. 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.
deleteMemory is provided by the ThinkMem MCP server (rickonono3/thinkmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThinkMem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 ThinkMem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.