List all stored conversation memories
AI agents call list_memories to retrieve information from MCP MITM Mem0 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a Read operation—it retrieves stored data without modifying it. However, severity is elevated to 'high' because: (1) the data being read consists of past conversations captured via MITM interception, which are inherently sensitive; (2) unrestricted listing of all memories could expose personal information, conversation history, user preferences, and context across sessions to an AI agent; (3)…
From the tool's definition Tool name 'list_memories' and description 'List all stored conversation memories' indicate data retrieval with no modification.
Attacks that exploit this kind of access
List all stored conversation memories. It is categorised as a Read tool in the MCP MITM Mem0 MCP Server, which means it retrieves data without modifying state.
Register the MCP MITM Mem0 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 MITM Mem0. 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 MITM Mem0 MCP server (terrymunro/mcp-mitm-mem0). 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 →