Get a value and its CAS token from the cache.
AI agents call cache_gets 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.
This tool retrieves a cached value along with its Compare-And-Swap token for optimistic locking scenarios. It performs a read-only query against the cache with no destructive, modifying, or executable side effects. The CAS token is metadata returned to support subsequent conditional writes, but the operation itself is purely a read operation.
From the tool's definition Tool name 'cache_gets' and description 'Get a value and its CAS token from the cache' indicate retrieval of data without modification or side effects.
Attacks that exploit this kind of access
Get a value and its CAS token from the cache. 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 cache_gets: 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.
cache_gets 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 cache_gets 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 cache_gets. 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.
cache_gets 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.