AI agents call search_memories to retrieve information from Mem0 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_memories' indicates a query or retrieval operation over stored memory data. Following MCP patterns and the presence of sibling tools (add_memory, delete_memory, update_memory, get_memory), this tool appears to search/filter existing memories without creating, modifying, or deleting them. This is consistent with Read category behavior.
From the tool's definition Tool name 'search_memories' implies querying/retrieval of memory data. Function name suggests read-only operation (search implies lookup without modification). No description provided, lowering confidence slightly.
Attacks that exploit this kind of access
search_memories. It is categorised as a Read tool in the Mem0 MCP Server, which means it retrieves data without modifying state.
Register the Mem0 MCP server in PolicyLayer and add a rule for search_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 Mem0. Nothing to install.
search_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 search_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 search_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.
search_memories is provided by the Mem0 MCP server (olk/mem0-mcp-server). 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 →