Search for memories based on various criteria
AI agents call search_memories to retrieve information from Claude Code Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from the Neo4j graph database without side effects. It has no capacity to create, modify, delete, or execute external operations. The blast radius of misuse is minimal—an agent could only retrieve information already stored in memory, with no destructive or irreversible consequences.
From the tool's definition Tool name 'search_memories' and description 'Search for memories based on various criteria' indicate a query/retrieval operation.
Documented attack patterns abuse exactly the kind of access search_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memories:
{
"version": "1",
"default": "deny",
"tools": {
"search_memories": {}
}
}search_memories 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.
Search for memories based on various criteria. It is categorised as a Read tool in the Claude Code Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Memory Server 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 Claude Code Memory Server. 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 Claude Code Memory Server MCP server (viralv00d00/claude-code-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Memory Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Claude Code Memory Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.