get_pricing
AI agents call get_pricing 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 retrieves pricing data from the ElastiCache/MemoryDB service. This is a read operation with no destructive, financial commitment, or execution capabilities. Even though it accesses pricing (financial context), it merely reads and returns information without authorizing transactions, moving money, or creating obligations.
From the tool's definition Tool name 'get_pricing' indicates retrieval of pricing information. Description is empty, but the name strongly suggests a read-only query operation that retrieves price data without modification or side effects.
Attacks that exploit this kind of access
get_pricing. 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 get_pricing: 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.
get_pricing 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 get_pricing 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 get_pricing. 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.
get_pricing 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.