AI agents call memory_search to retrieve information from Exocortex 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 stored memory data without side effects. It is a search/retrieval operation that returns results based on input parameters. There is no capability to modify, execute code, delete data, or commit financial transactions. This is a classic 'Read' operation in the context of a personal memory system.
From the tool's definition Tool name is 'memory_search' and description indicates it 'searches' memories using hybrid search (semantic + keyword + graph). Parameters like 'compact', 'expanded_query', and 'max_tokens' control retrieval format and result size, not data modification.
Attacks that exploit this kind of access
Hybrid search (semantic + keyword + graph). Use compact: true for previews, expanded_query for better recall, max_tokens for budget-packed results. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_search: 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 Exocortex. Nothing to install.
memory_search 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 memory_search 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 memory_search. 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.
memory_search is provided by the Exocortex MCP server (shawnhack/exocortex). 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 →