gateway_list
AI agents call gateway_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 suggests listing or querying gateway information without side effects. No description is provided, so confidence is moderate rather than high. The 'list' operation pattern is characteristic of Read operations. Given the ElastiCache/MemoryDB context and the innocuous nature of simply enumerating resources, this is low severity.
From the tool's definition Tool named 'gateway_list' on an ElastiCache/MemoryDB Valkey server; the 'list' suffix indicates a query/retrieval operation that enumerates gateways without modification.
Attacks that exploit this kind of access
gateway_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 gateway_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.
gateway_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 gateway_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 gateway_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.
gateway_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.