memory_list_events
AI agents call memory_list_events 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 pattern 'list_*' strongly suggests a read-only operation that queries and returns event data from the MemoryDB/Valkey cache system. However, confidence is moderate (0.7) rather than high because the description is empty, making it impossible to confirm exact behavior, parameters, or scope. No evidence of side effects, data modification, or destructive operations is apparent from the name alone.
From the tool's definition Tool name is 'memory_list_events' which indicates a list operation that retrieves events without modification.
Attacks that exploit this kind of access
memory_list_events. 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_events: 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_events 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_events 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_events. 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_events 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.