List memories with optional filtering by tags or types.
AI agents call memory_list to retrieve information from MCP Router without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays stored memory records without modifying, deleting, or executing any operations. It is a straightforward query function that allows filtering but does not alter state. The presence of access controls on the MCP Router platform mitigates read-based information disclosure risks, keeping severity low.
From the tool's definition Tool name 'memory_list' and description 'List memories with optional filtering by tags or types' indicate a retrieval operation with no side effects. The verb 'list' and the ability to filter (query parameters) are characteristic of read-only data access.
Attacks that exploit this kind of access
List memories with optional filtering by tags or types. It is categorised as a Read tool in the MCP Router MCP Server, which means it retrieves data without modifying state.
Register the MCP Router MCP server in PolicyLayer and add a rule for memory_list: 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 MCP Router. Nothing to install.
memory_list 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 memory_list 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 memory_list. 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.
memory_list is provided by the MCP Router MCP server (justinpreston/mcp-router). 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 →