Hybrid (vector + BM25) search over stored memories.
AI agents call search_memory to retrieve information from N3MemoryCore Lite (Working Memory) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from memory storage using hybrid search (vector + BM25). It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal; an agent could retrieve unwanted information but cannot alter system state or trigger external actions. It fits the 'Read' category unambiguously.
From the tool's definition Tool description states it performs 'search over stored memories' with no mention of modification, deletion, or execution capabilities. The verb 'search' and the read-only operation of querying stored data are unambiguous.
Attacks that exploit this kind of access
Hybrid (vector + BM25) search over stored memories. It is categorised as a Read tool in the N3MemoryCore Lite (Working Memory) MCP Server, which means it retrieves data without modifying state.
Register the N3MemoryCore Lite (Working Memory) 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 N3MemoryCore Lite (Working Memory). 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 N3MemoryCore Lite (Working Memory) MCP server (NeuralNexusNote/n3mcmcp-lite). 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 →