list_canaries
AI agents call list_canaries 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 'list' prefix strongly indicates this tool retrieves or enumerates canaries (monitoring checks) without modifying them. This aligns with the Read category for data retrieval operations. Confidence is 0.85 rather than higher due to the empty description, but the naming convention is decisive for classification. Severity is low as listing canaries has minimal blast radius.
From the tool's definition Tool name is 'list_canaries' which indicates a retrieval/query operation. The description is empty, but the name pattern follows standard enumeration conventions (list_*).
Attacks that exploit this kind of access
list_canaries. 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_canaries: 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_canaries 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_canaries 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_canaries. 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_canaries 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.