memory_list_records
AI agents call memory_list_records 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.
List operations are characteristic Read tools that retrieve data without side effects. The empty description reduces confidence slightly, but the naming convention is consistent with non-destructive data retrieval in AWS contexts. No evidence of write, delete, execute, or financial operations.
From the tool's definition Tool name 'memory_list_records' indicates a list operation, which is a read-only query pattern. The 'list' prefix strongly suggests retrieval of records without modification.
Attacks that exploit this kind of access
memory_list_records. 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_records: 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_records 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_records 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_records. 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_records 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.