Low Risk

list_all_memories

Retrieve all saved memories.

How to control list_all_memories ↓

What list_all_memories does on A-Modular-Kingdom

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

Low Risk

Why list_all_memories needs a policy

This tool retrieves or queries data (all saved memories) without creating, modifying, or deleting information. It matches the Read category profile: a simple data retrieval with no mutation capability. Severity is low because listing memories poses minimal risk even if misused by an AI agent—it gathers information but cannot alter system state. Confidence is high given the clear read-only semantics.

From the tool's definition Tool name 'list_all_memories' and description 'Retrieve all saved memories' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_all_memories gives an agent:

How to control list_all_memories

PolicyLayer is an MCP gateway — it sits between your AI agents and A-Modular-Kingdom, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_memories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_all_memories": {}
  }
}

list_all_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register A-Modular-Kingdom — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_all_memories

What does the list_all_memories tool do? +

Retrieve all saved memories. It is categorised as a Read tool in the A-Modular-Kingdom MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_memories? +

Register the A-Modular-Kingdom MCP server in PolicyLayer and add a rule for list_all_memories: 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 A-Modular-Kingdom. Nothing to install.

What risk level is list_all_memories? +

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

Can I rate-limit list_all_memories? +

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

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

list_all_memories is provided by the A-Modular-Kingdom MCP server (masihmoafi/a-modular-kingdom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A-Modular-Kingdom tool call.

Start from A-Modular-Kingdom, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 A-Modular-Kingdom tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.