AI agents call deleteListElementByName 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 deletes data from memory structures without reversibility. While the blast radius is limited to memory elements rather than critical system resources, the destruction of stored information qualifies as Destructive rather than Write. The high severity reflects that an errant agent could lose important contextual information, though the impact is scoped to a single memory list rather than broader system data.
From the tool's definition Tool name contains 'delete' and description states '删除ListMemory中的指定元素' (delete specified elements in ListMemory). The operation irreversibly removes data from memory storage.
Documented attack patterns abuse exactly the kind of access deleteListElementByName 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 deleteListElementByName:
{
"version": "1",
"default": "deny",
"hide": [
"deleteListElementByName"
]
}deleteListElementByName 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.
根据元素名称删除ListMemory中的指定元素，利用名称唯一性机制定位。. 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 deleteListElementByName: 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.
deleteListElementByName 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 deleteListElementByName 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 deleteListElementByName. 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.
deleteListElementByName 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.