List recent memories by creation time (newest first). Supports same filters as search_memory: categories, tags, observation_types, concepts. Returns id (use as memory_id for delete), content, category, observation_type, concepts, tags.
AI agents call list_memory to retrieve information from Memoryx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | Optional. Filter by tags |
limit | number | — | Max items, default 20 |
offset | number | — | Pagination offset, default 0 |
concepts | array | — | Optional. Filter by concepts (how-it-works/why-it-exists/what-changed/problem-solution/gotcha/pattern/trade-off) |
categories | array | — | Optional. Filter by category |
time_filter | object | — | Optional. start/end YYYY-MM-DD HH:mm:ss |
observation_types | array | — | Optional. Filter by observation_type (bugfix/feature/refactor/change/discovery/decision) |
Parameters from the server's own tool schema.
This tool retrieves and queries stored memory records with optional filtering. It is a passive read operation that does not create, modify, delete, or execute anything. The severity is low because listing memories poses minimal risk—it only exposes data already accessible to the agent and does not alter state or trigger external operations.
From the tool's definition Tool name 'list_memory' and description 'List recent memories' indicates retrieval of data. Returns id, content, category, observation_type, concepts, tags with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
List recent memories by creation time (newest first). Supports same filters as search_memory: categories, tags, observation_types, concepts. Returns id (use as memory_id for delete), content, category, observation_type, concepts, tags. It is categorised as a Read tool in the Memoryx MCP Server, which means it retrieves data without modifying state.
list_memory accepts 7 parameters: tags, limit, offset, concepts, categories, time_filter, observation_types. The full parameter table on this page comes from the server's own tool schema.
Register the Memoryx MCP server in PolicyLayer and add a rule for list_memory: 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 Memoryx. Nothing to install.
list_memory 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 list_memory 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 list_memory. 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.
list_memory is provided by the Memoryx MCP server (@t0ken.ai/memoryx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →