list-delivery-streams
AI agents call list-delivery-streams 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 strongly suggests querying or enumerating delivery streams from AWS services (likely Kinesis Data Firehose or similar). List operations are Read category with low severity unless they expose sensitive data en masse. Confidence is moderate (0.7) due to missing description, but the naming convention is clear enough to confidently categorize as Read rather than Write or Execute.
From the tool's definition Tool name 'list-delivery-streams' indicates a listing/enumeration operation. The 'list' prefix is characteristic of Read operations that retrieve information without modification. No description provided to confirm or refine classification.
Attacks that exploit this kind of access
list-delivery-streams. 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 list-delivery-streams: 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.
list-delivery-streams 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 list-delivery-streams 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 list-delivery-streams. 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.
list-delivery-streams 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.