ListPullThroughCacheRules
AI agents call ListPullThroughCacheRules 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' verb pattern is characteristic of Read operations that retrieve configuration or metadata. Without a description, confidence is reduced, but the naming convention strongly suggests this tool queries pull-through cache rules in ElastiCache/MemoryDB without side effects. No execution, modification, or deletion of data is implied.
From the tool's definition Tool name 'ListPullThroughCacheRules' uses the verb 'List', which indicates querying or retrieving existing cache rules without modifying them.
Attacks that exploit this kind of access
ListPullThroughCacheRules. 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 ListPullThroughCacheRules: 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.
ListPullThroughCacheRules 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 ListPullThroughCacheRules 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 ListPullThroughCacheRules. 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.
ListPullThroughCacheRules 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.