AI agents use move_list_item to create or update resources in Mcp Structured Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Structured Memory environment.
This tool creates or modifies data in a reversible manner by relocating list items between sections. It does not irreversibly delete data (Destructive), execute arbitrary code (Execute), or trigger financial transactions (Financial). While it does alter stored state, the operation is reversible—items can be moved back. This is characteristic of Write operations.
From the tool's definition The tool description states 'Move an item from one section to another', which modifies the structure and location of stored data within the memory system. The verb 'move' indicates a reversible reorganization of existing list items.
Documented attack patterns abuse exactly the kind of access move_list_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Structured Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for move_list_item:
{
"version": "1",
"default": "deny",
"tools": {
"move_list_item": {
"limits": [
{
"counter": "move_list_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_list_item 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.
Move an item from one section to another. It is categorised as a Write tool in the Mcp Structured Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Structured Memory MCP server in PolicyLayer and add a rule for move_list_item: 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 Mcp Structured Memory. Nothing to install.
move_list_item 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 move_list_item 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 move_list_item. 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.
move_list_item is provided by the Mcp Structured Memory MCP server (nmeierpolys/mcp-structured-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Structured Memory, 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.
10 Mcp Structured Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.