Low Risk

list_memories

List all your stored memories.

How to control list_memories ↓

What list_memories does on Open WebUI MCP Server

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

Low Risk

Why list_memories needs a policy

This tool performs a simple query operation to retrieve stored memories without any side effects, modification, deletion, or execution of external operations. It has minimal blast radius if misused by an AI agent—the worst outcome would be unauthorized data disclosure of the user's own memories. This fits the Read category (retrieves data; no side effects).

From the tool's definition Tool name 'list_memories' and description 'List all your stored memories' indicate a data retrieval operation with no modification or deletion capability. The verb 'list' is a classic Read operation that only queries and returns existing data.

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

How to control list_memories

PolicyLayer is an MCP gateway — it sits between your AI agents and Open WebUI MCP Server, 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 Open WebUI MCP Server — 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_memories

What does the list_memories tool do? +

List all your stored memories. It is categorised as a Read tool in the Open WebUI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_memories? +

Register the Open WebUI MCP Server 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 Open WebUI MCP Server. 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 Open WebUI MCP Server MCP server (troylar/open-webui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Open WebUI MCP Server tool call.

Start from Open WebUI MCP Server, 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.

82 Open WebUI MCP Server 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.