AI agents call memory_list to retrieve information from Cortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to enumerate or list stored memory entries from the Cortex vault—a read-only operation. Even if it returns sensitive personal context or previous decisions, listing does not modify or delete data, nor does it execute external code or move funds. The empty description lowers confidence slightly, but the naming convention and context place it clearly in the Read category.
From the tool's definition Tool name 'memory_list' suggests listing/querying memory entries. The description is empty, but the sibling tools (memory_get, memory_recall, memory_remind, memory_graph) and the server's purpose (persistent memory retrieval) indicate this retrieves stored…
Documented attack patterns abuse exactly the kind of access memory_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_list:
{
"version": "1",
"default": "deny",
"tools": {
"memory_list": {}
}
}memory_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
memory_list. It is categorised as a Read tool in the Cortex MCP Server, which means it retrieves data without modifying state.
Register the Cortex 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 Cortex. 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 Cortex MCP server (tt-wang/memem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cortex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Cortex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.