Add an item to a list section in a memory document
AI agents use add_to_list 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.
The tool adds entries to a list within a memory document, which is a create/modify operation without side effects beyond the memory store itself. This is a Write category action — the modification is reversible and has minimal blast radius even if misused by an agent. No data is destroyed, no external operations triggered, and no financial impact.
From the tool's definition Tool description states 'Add an item to a list section in a memory document' — this creates/modifies data in a reversible manner (items can be removed or edited later).
Documented attack patterns abuse exactly the kind of access add_to_list 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 add_to_list:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_list": {
"limits": [
{
"counter": "add_to_list_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_to_list 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.
Add an item to a list section in a memory document. 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 add_to_list: 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.
add_to_list 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 add_to_list 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 add_to_list. 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.
add_to_list 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.