Keyword search across all indexed agent session transcripts, ranked by relevance (bm25).
AI agents call search_memory to retrieve information from Lore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and searches historical session data without creating, modifying, deleting, or executing any operations. This is a pure read operation that queries indexed transcripts. The low severity reflects minimal risk even if an agent searches for sensitive information, as no data is altered, deleted, or processed beyond return of search results.
From the tool's definition Tool description states it performs 'Keyword search across all indexed agent session transcripts, ranked by relevance' — a retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access search_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lore, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memory:
{
"version": "1",
"default": "deny",
"tools": {
"search_memory": {}
}
}search_memory 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.
Keyword search across all indexed agent session transcripts, ranked by relevance (bm25). It is categorised as a Read tool in the Lore MCP Server, which means it retrieves data without modifying state.
Register the Lore 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 Lore. 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 Lore MCP server (jordanhindo/lore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lore, 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 Lore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.