在栈模式ListMemory的顶部添加新元素，遵循后进先出原则。
AI agents use pushStackElement 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 modifies memory state by pushing an element onto a stack, which is a reversible write operation. It does not execute arbitrary code, delete data permanently, move financial resources, or retrieve data without side effects.
From the tool's definition The tool name 'pushStackElement' and description ('添加新元素' = 'add new element') indicate it creates/modifies data in a stack structure. The LIFO (last-in-first-out) principle confirms this is a write operation that adds elements to memory.
Documented attack patterns abuse exactly the kind of access pushStackElement 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 pushStackElement:
{
"version": "1",
"default": "deny",
"tools": {
"pushStackElement": {
"limits": [
{
"counter": "pushstackelement_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pushStackElement 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 pushStackElement: 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.
pushStackElement 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 pushStackElement 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 pushStackElement. 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.
pushStackElement 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.