Search saved OpenMembrane memory by query, scope, type, tag, or project.
AI agents call search_memory to retrieve information from OpenMemBrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves stored memory data based on various filter parameters. It has no side effects — it only reads and returns information. This is a standard Read category operation. Severity is low because searching memory poses minimal risk; the worst outcome is information disclosure of what has already been stored, with no capability to modify systems or execute operations.
From the tool's definition Tool name is 'search_memory' and description states it 'Search[es] saved OpenMembrane memory by query, scope, type, tag, or project.' This is a pure retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Search saved OpenMembrane memory by query, scope, type, tag, or project. It is categorised as a Read tool in the OpenMemBrain MCP Server, which means it retrieves data without modifying state.
Register the OpenMemBrain 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 OpenMemBrain. 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 OpenMemBrain MCP server (mohamadalhusseinie/openmembrain). 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 →