AI agents call clearList 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 and irreversibly deletes all data stored in a ListMemory structure. There is no recovery mechanism or undo capability. The impact severity is high because an AI agent misusing this could lose critical memory data that the LLM depends on for context and information management. This is categorized as Destructive rather than Write because the action cannot be undone and results in total data loss.
From the tool's definition Tool description states '清空ListMemory中的所有元素，此操作不可逆' which translates to 'Clear all elements in ListMemory, this operation is irreversible.' The explicit mention of irreversibility (不可逆) and the destructive nature of clearing all elements confirms this is a…
Documented attack patterns abuse exactly the kind of access clearList 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 clearList:
{
"version": "1",
"default": "deny",
"hide": [
"clearList"
]
}clearList 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 clearList: 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.
clearList 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 clearList 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 clearList. 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.
clearList 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.