get-billing-group-cost-report
AI agents call get-billing-group-cost-report 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 billing cost report data (read operation) with no capability to modify, delete, or execute code. While it accesses potentially sensitive financial data, the action itself is non-destructive. Classified as Read with medium-low severity due to information sensitivity, though the specific scope and access controls are unclear given the empty description.
From the tool's definition Tool name 'get-billing-group-cost-report' indicates retrieval of billing/cost data; description is empty but the name clearly suggests a read operation that queries existing cost report information.
Attacks that exploit this kind of access
get-billing-group-cost-report. 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-billing-group-cost-report: 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-billing-group-cost-report 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-billing-group-cost-report 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-billing-group-cost-report. 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-billing-group-cost-report 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.