创建一个新的ListMemory存储块,作为有序集合使用。支持array(数组)、deque(双端队列)、stack(栈)三种角色模式。
AI agents use addListMemory to create or update resources in ThinkMem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ThinkMem environment.
This tool creates and initializes new data structures within the memory system. While reversible (can be deleted via sibling tool deleteMemory), it modifies the agent's persistent memory state. This is Write-category behavior: creates/initializes data structures.
From the tool's definition Tool creates a new ListMemory storage block ("创建一个新的ListMemory存储块"), which is a data structure creation operation. Description explicitly states it creates memory storage with support for three role modes (array, deque, stack).
Documented attack patterns abuse exactly the kind of access addListMemory 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 addListMemory:
{
"version": "1",
"default": "deny",
"tools": {
"addListMemory": {
"limits": [
{
"counter": "addlistmemory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} addListMemory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
创建一个新的ListMemory存储块,作为有序集合使用。支持array(数组)、deque(双端队列)、stack(栈)三种角色模式。. It is categorised as a Write tool in the ThinkMem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ThinkMem MCP server in PolicyLayer and add a rule for addListMemory: 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.
addListMemory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the addListMemory 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 addListMemory. 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.
addListMemory 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.