List all memories, optionally filtered by project and/or category.
AI agents call list_memories to retrieve information from mcp-Agentmemory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries memory data without modifying, deleting, or executing any actions. It is a straightforward read operation that returns filtered lists of stored information. The only risk is potential information disclosure if memories contain sensitive data, but that is low severity in the context of an AI memory system designed for a trusted development environment.
From the tool's definition Tool name 'list_memories' and description 'List all memories, optionally filtered by project and/or category' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all memories, optionally filtered by project and/or category. It is categorised as a Read tool in the mcp-Agentmemory MCP Server, which means it retrieves data without modifying state.
Register the mcp-Agentmemory 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-Agentmemory. 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-Agentmemory MCP server (obidel/agentmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →