list-pricing-rules-for-plan
AI agents call list-pricing-rules-for-plan 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 tool name strongly suggests it retrieves or enumerates pricing rules associated with a plan. This is a read-only query operation with no side effects. Even in the context of ElastiCache/MemoryDB services, listing pricing information is informational retrieval rather than modification, execution, or destructive action.
From the tool's definition Tool name 'list-pricing-rules-for-plan' uses the 'list' prefix, which indicates data retrieval. The description is empty, limiting certainty.
Attacks that exploit this kind of access
list-pricing-rules-for-plan. 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-pricing-rules-for-plan: 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-pricing-rules-for-plan 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-pricing-rules-for-plan 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-pricing-rules-for-plan. 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-pricing-rules-for-plan 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.