list-cost-allocation-tags
AI agents call list-cost-allocation-tags 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 name indicates a query/list operation that retrieves cost allocation tags for informational/billing purposes. This is read-only access with no side effects. Confidence is moderate (0.6) because the description is empty, preventing full verification of the tool's actual behavior and scope.
From the tool's definition Tool name 'list-cost-allocation-tags' suggests retrieval of cost allocation tag metadata; no description provided.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
list-cost-allocation-tags. 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-allocation-tags: 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-allocation-tags 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-allocation-tags 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-allocation-tags. 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-allocation-tags 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.