memory_search_unified
Search across both Claude Code memories and AgentDB entries using semantic vector similarity. Returns merged, deduplicated results from all namespaces. Use when native Read/Write is wrong because you need (a) cross-session retrieval by semantic similarity (vector embeddings) not by file path, (b)...
This record as markdown: /tools/ruflo/memory-search-unified.md
What memory_search_unified does on Ruflo
AI agents call memory_search_unified to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why memory_search_unified is rated Low
This is a pure retrieval operation that queries existing data using semantic similarity without side effects. It searches memories and database entries but does not create, modify, delete, or execute anything. The tool explicitly acknowledges it is for 'Read' operations and contrasts itself with native 'Read/Write' for practical reasons (semantic indexing vs file paths), reinforcing its read-only nature.
From the tool's definition Tool performs 'Search across both Claude Code memories and AgentDB entries using semantic vector similarity. Returns merged, deduplicated results' with explicit guidance to use it for 'cross-session retrieval' and 'audit trail' inspection.
Attacks that exploit this kind of access
The rule that runs memory_search_unified safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_search_unified, this is the rule to start with:
memory_search_unified is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every memory_search_unified call is checked against it from then on.
Questions about memory_search_unified
Search across both Claude Code memories and AgentDB entries using semantic vector similarity. Returns merged, deduplicated results from all namespaces. Use when native Read/Write is wrong because you need (a) cross-session retrieval by semantic similarity (vector embeddings) not by file path, (b) namespacing across projects without managing directory layout, or (c) the .swarm/memory.db audit trail. For one-shot file I/O, native Read/Write is fine. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for memory_search_unified: 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 Ruflo. Nothing to install.
memory_search_unified 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_unified 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_unified. 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_unified is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue