Hybrid search with intelligent cache/cloud routing and relevance scoring
AI agents call search_memory to retrieve information from r3 (Recall) 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 memory storage (local Redis cache and optional cloud) and returns results with relevance scores. It performs semantic search—a read-only operation with no side effects on the underlying data. While it may invoke cloud routing logic, the tool's primary function is data retrieval, not creation, modification, deletion, or execution of arbitrary code.
From the tool's definition Tool name 'search_memory' and description 'Hybrid search with intelligent cache/cloud routing and relevance scoring' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Hybrid search with intelligent cache/cloud routing and relevance scoring. It is categorised as a Read tool in the r3 (Recall) MCP Server, which means it retrieves data without modifying state.
Register the r3 (Recall) MCP server in PolicyLayer and add a rule for search_memory: 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 r3 (Recall). Nothing to install.
search_memory 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_memory 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_memory. 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_memory is provided by the r3 (Recall) MCP server (n3wth/r3). 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 →