AI agents call list_memories to retrieve information from Engram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists stored memories with optional filters (category, tag, metadata, date range) and returns results sorted by recency. It is a read-only operation that queries data without side effects, matching the Read category definition (search, list, get, fetch). The low severity reflects minimal blast radius—misuse would only expose existing data, not modify or delete it.
From the tool's definition Tool name 'list_memories' and description 'Lista memorias con filtros opcionales por categoría, tag, metadata o rango de fechas. Retorna las más recientes primero por defecto' indicate querying/listing functionality with optional filtering parameters.
Attacks that exploit this kind of access
Lista memorias con filtros opcionales por categoría, tag, metadata o rango de fechas. Retorna las más recientes primero por defecto. It is categorised as a Read tool in the Engram MCP Server, which means it retrieves data without modifying state.
Register the Engram 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 Engram. Nothing to install.
list_memories 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_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.
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.
list_memories is provided by the Engram MCP server (jacksini/engram-mcp). 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 →