LIST BROWSE SHOW ALL - List all stored memories chronologically. Use when search returns nothing or to explore what is stored. Keywords: list, browse, show, display, view all, get all, see memories, show history, list facts, display knowledge, browse storage, what is stored, show everything, rece...
AI agents call memory_list to retrieve information from MCP AI Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves and displays existing memory data. There are no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an agent could view all stored memories but cannot alter, delete, or act upon them in harmful ways. This fits the 'Read' category for data retrieval operations.
From the tool's definition Tool name 'memory_list' and description explicitly states 'LIST BROWSE SHOW ALL - List all stored memories chronologically' with keywords including 'list, browse, show, display, view all, get all'.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access memory_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP AI Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_list:
{
"version": "1",
"default": "deny",
"tools": {
"memory_list": {}
}
}memory_list 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 BROWSE SHOW ALL - List all stored memories chronologically. Use when search returns nothing or to explore what is stored. Keywords: list, browse, show, display, view all, get all, see memories, show history, list facts, display knowledge, browse storage, what is stored, show everything, recent memories. It is categorised as a Read tool in the MCP AI Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP AI Memory MCP server in PolicyLayer and add a rule for memory_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 AI Memory. Nothing to install.
memory_list 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 memory_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 memory_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.
memory_list is provided by the MCP AI Memory MCP server (scanadi/mcp-ai-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 MCP AI Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 MCP AI Memory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.