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)...

Server Ruflo ruvnet/ruflo
Category Read
Risk class Low
Parameters 00 required

What memory_search_unified does on Ruflo

AI agents call memory_search_unified to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why memory_search_unified needs a policy

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.

Questions about memory_search_unified

What does the memory_search_unified tool do? +

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.

How do I enforce a policy on memory_search_unified? +

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.

What risk level is memory_search_unified? +

memory_search_unified is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_search_unified? +

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.

How do I block memory_search_unified completely? +

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.

What MCP server provides memory_search_unified? +

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.

// THE FULL RECORD

memory_search_unified is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.