memory_bridge_status
Show Claude Code memory bridge status — AgentDB vectors, SONA learning, intelligence patterns, and connection health. 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 witho...
This record as markdown: /tools/io-github-ruvnet-claude-flow/memory-bridge-status.md
What memory_bridge_status does on Claude Flow
AI agents call memory_bridge_status 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.
Why memory_bridge_status is rated Low
This tool retrieves and displays status information about a memory system, AgentDB vectors, learning patterns, and connection health. The verb 'Show' and context of querying embeddings, namespacing, and audit trails confirm it is a Read operation. There are no side effects, modifications, or irreversible actions.
From the tool's definition Tool description states 'Show Claude Code memory bridge status' and explicitly lists retrieval operations: 'cross-session retrieval by semantic similarity (vector embeddings)', 'namespacing across projects', and 'audit trail' review.
Attacks that exploit this kind of access
The rule that runs memory_bridge_status 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_bridge_status, this is the rule to start with:
memory_bridge_status 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 Claude Flow, apply this rule, and every memory_bridge_status call is checked against it from then on.
Questions about memory_bridge_status
Show Claude Code memory bridge status — AgentDB vectors, SONA learning, intelligence patterns, and connection health. 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 Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for memory_bridge_status: 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.
memory_bridge_status 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_bridge_status 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_bridge_status. 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_bridge_status 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.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue