list-cost-category-definitions
AI agents call list-cost-category-definitions 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.
List operations are non-destructive retrievals of existing data with no side effects. The tool appears designed to enumerate cost category definitions in what is likely an AWS billing or cost management context. While the description is empty, the name itself clearly indicates a data retrieval function, not a write, execute, or destructive action.
From the tool's definition The tool name 'list-cost-category-definitions' uses the verb 'list', which is a quintessential Read operation that retrieves or queries data. The empty description provides no contradictory evidence about the tool's purpose.
Attacks that exploit this kind of access
list-cost-category-definitions. 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-cost-category-definitions: 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-cost-category-definitions 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-cost-category-definitions 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-cost-category-definitions. 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-cost-category-definitions 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.