AI agents call list_memories to retrieve information from Mcp Structured Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing memory documents without creating, modifying, or deleting data. It is a read-only operation that enumerates available resources, consistent with the 'Read' category for retrieval tools like 'list' and 'get'.
From the tool's definition Tool name 'list_memories' and description 'List all available memory documents' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_memories 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 list_memories:
{
"version": "1",
"default": "deny",
"tools": {
"list_memories": {}
}
} list_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available memory documents. It is categorised as a Read tool in the Mcp Structured Memory MCP Server, which means it retrieves data without modifying state.
Register the Mcp Structured Memory MCP server in PolicyLayer and add a rule for list_memories: 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.
list_memories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_memories 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 list_memories. 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.
list_memories 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.