在双端队列模式ListMemory的前端或后端添加元素。
AI agents use pushDequeElement 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.
The tool's function is to insert elements into a deque-based memory structure. This is a write operation that modifies the state of the memory system but can be reversed (elements can be removed via deleteListElement or similar tools). It does not delete data irreversibly, execute arbitrary code, or involve financial operations, so Write is the appropriate category rather than the more severe categories.
From the tool's definition Tool name 'pushDequeElement' and description indicating it adds elements ('添加元素') to a double-ended queue (deque) in ListMemory, which is a data structure modification operation. This creates or modifies data in the memory system reversibly.
Documented attack patterns abuse exactly the kind of access pushDequeElement 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 pushDequeElement:
{
"version": "1",
"default": "deny",
"tools": {
"pushDequeElement": {
"limits": [
{
"counter": "pushdequeelement_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pushDequeElement 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的前端或后端添加元素。. 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 pushDequeElement: 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.
pushDequeElement 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 pushDequeElement 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 pushDequeElement. 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.
pushDequeElement 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.