memory_search

Search semantic memory using HNSW

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/memory-search.md

WHAT IT DOES

What memory_search does on Claude Flow

AI agents call memory_search to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why memory_search is rated Low

This tool retrieves or queries data from a semantic memory store without side effects. It is purely informational and does not create, modify, delete, or execute any operations. The low severity reflects minimal blast radius—a misused search query cannot corrupt data or trigger unintended external actions.

From the tool's definition Tool performs a 'Search' operation on 'semantic memory' with no indication of modification, deletion, or execution. The HNSW (Hierarchical Navigable Small World) algorithm is a read-only vector search mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_search, this is the rule to start with:

memory_search Allowed

memory_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every memory_search call is checked against it from then on.

FAQ

Questions about memory_search

What does the memory_search tool do? +

Search semantic memory using HNSW. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_search? +

Register the Claude Flow 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 Claude Flow. Nothing to install.

What risk level is memory_search? +

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

Can I rate-limit memory_search? +

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.

How do I block memory_search completely? +

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.

What MCP server provides memory_search? +

memory_search is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →