readonly_query
AI agents call readonly_query 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.
Despite the empty description limiting confidence, the tool name strongly suggests this performs read-only query operations against the ElastiCache/MemoryDB Valkey cache. Read-only operations retrieve data without side effects, making this a Read category tool with low severity risk since it cannot modify, delete, or execute code.
From the tool's definition Tool name is 'readonly_query' which explicitly indicates read-only access. The 'readonly' prefix combined with 'query' operation clearly signals data retrieval without modification.
Attacks that exploit this kind of access
readonly_query. 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 readonly_query: 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.
readonly_query 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 readonly_query 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 readonly_query. 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.
readonly_query 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.