memory_list
AI agents call memory_list to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'memory_list' clearly follows the read pattern (list operation). While the description is empty, the naming convention strongly suggests this retrieves or enumerates cache data. There is no evidence of modification, deletion, or execution. The blast radius of an accidental misuse is minimal—listing cache contents cannot damage systems or data.
From the tool's definition Tool name 'memory_list' and the server context (ElastiCache/MemoryDB Valkey) indicate a list/query operation that retrieves memory cache entries or metadata without modifying state.
Attacks that exploit this kind of access
memory_list. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.