list-cost-allocation-tag-backfill-history
AI agents call list-cost-allocation-tag-backfill-history 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 'list' prefix strongly indicates a read-only operation that retrieves historical information. Although the description is empty (lowering confidence slightly), the tool name pattern is consistent with AWS operations that return logs or history without side effects.
From the tool's definition Tool name 'list-cost-allocation-tag-backfill-history' contains the verb 'list', which retrieves or queries historical data about cost allocation tag backfill operations without modifying or deleting anything.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
list-cost-allocation-tag-backfill-history. 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-tag-backfill-history: 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-tag-backfill-history 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-tag-backfill-history 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-tag-backfill-history. 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-tag-backfill-history 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.