cost-anomaly
AI agents call cost-anomaly 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 naming convention, this tool likely retrieves and analyzes cost anomaly data without modifying, deleting, or executing operations. The absence of a description and the generic context among other AWS operational tools suggests a monitoring or analysis function. However, low confidence due to missing documentation.
From the tool's definition Tool name 'cost-anomaly' suggests analysis or detection of cost anomalies, which is a read operation on existing cost/usage data. No description provided to confirm, reducing confidence.
Attacks that exploit this kind of access
cost-anomaly. 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 cost-anomaly: 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.
cost-anomaly 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 cost-anomaly 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 cost-anomaly. 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.
cost-anomaly 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.