storage-lens
AI agents call storage-lens 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.
Although the description is empty, the tool name indicates a read-only analytics/monitoring function. 'Lens' metaphorically suggests inspection rather than modification or execution. However, confidence is reduced to 0.6 due to the lack of descriptive detail. If Storage Lens were misconfigured to expose write or execute capabilities, the category could shift to Write or Execute with more information.
From the tool's definition Tool name 'storage-lens' suggests a data inspection/analytics capability typical of AWS Storage Lens, which retrieves metrics and configuration data without modifying resources.
Attacks that exploit this kind of access
storage-lens. 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 storage-lens: 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.
storage-lens 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 storage-lens 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 storage-lens. 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.
storage-lens 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.