memory_list

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-list.md

WHAT IT DOES

What memory_list does on Claude Flow

AI agents call memory_list 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_list is rated Low

memory_list performs enumeration and inspection of stored data without side effects. It retrieves or queries memory entries from a database, matching the Read category pattern. The low severity reflects that simple enumeration of memory metadata poses minimal risk even if misused by an agent—no data is modified, deleted, or executed.

From the tool's definition Tool description explicitly states 'Enumerate stored memory entries' and 'Use when native Glob is wrong because the entries are not files'. The verb 'enumerate' and context of 'inspection / audit' confirm read-only retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_list 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_list, this is the rule to start with:

memory_list Allowed

memory_list 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_list": {}
  }
}

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_list call is checked against it from then on.

FAQ

Questions about memory_list

What does the memory_list tool do? +

Enumerate stored memory entries (optionally filtered by namespace/tags) without semantic search. Use when native Glob is wrong because the entries are not files (they live in .swarm/memory.db). For inspection / audit /. 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_list? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for memory_list: 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_list? +

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

Can I rate-limit memory_list? +

Yes. Add a rate_limit block to the memory_list 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_list completely? +

Set action: deny in the PolicyLayer policy for memory_list. 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_list? +

memory_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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