get-cost-and-usage
AI agents call get-cost-and-usage 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.
Based on the name, this tool retrieves or queries cost and usage information from AWS. The 'get-' prefix strongly suggests a read operation with no side effects. However, the empty description reduces confidence slightly. Cost and usage data is sensitive but read-only access poses minimal risk if misused by an agent (information disclosure rather than destructive/financial action).
From the tool's definition Tool name 'get-cost-and-usage' indicates retrieval of cost and usage data without modification. Description is empty, limiting certainty.
Attacks that exploit this kind of access
get-cost-and-usage. 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-cost-and-usage: 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-cost-and-usage 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-cost-and-usage 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-cost-and-usage. 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-cost-and-usage 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.