Low Risk

list_memories

List all stored memories with metadata. Optionally filter by type.

How to control list_memories ↓

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

Low Risk

This tool retrieves and displays stored metadata about memories. It performs a read-only query with filtering capability, which is non-destructive and has no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could at worst view internal memory metadata, which is low-severity information disclosure.

From the tool's definition Tool name 'list_memories' and description 'List all stored memories with metadata. Optionally filter by type.' indicate a retrieval/query operation with no data modification or side effects.

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

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

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

list_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 Reporecall — 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.

Go deeper

What does the list_memories tool do? +

List all stored memories with metadata. Optionally filter by type. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_memories? +

Register the Reporecall MCP server in PolicyLayer and add a rule for list_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 Reporecall. Nothing to install.

What risk level is list_memories? +

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

Can I rate-limit list_memories? +

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

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

list_memories is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ 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.