Search through saved memories by keyword. Returns matching rules/facts.
AI agents call search_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.
The tool performs a query operation that searches and retrieves data from stored memories without creating side effects. It falls clearly into the Read category as it only fetches and returns information based on search criteria. The severity is low because misuse would only expose information already stored in the system, with no capacity for unauthorized modification, deletion, or external operations.
From the tool's definition Tool description states "Search through saved memories by keyword. Returns matching rules/facts." This is a retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search through saved memories by keyword. Returns matching rules/facts. 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 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 mcp-Agentmemory. 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 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 →