list-cost-allocation-tag-backfill-history

list-cost-allocation-tag-backfill-history

Server AWS IoT SiteWise MCP Server awslabs.aws-iot-sitewise-mcp-server
Category Read
Risk class Low
Parameters 00 required

What list-cost-allocation-tag-backfill-history does on AWS IoT SiteWise MCP Server

AI agents call list-cost-allocation-tag-backfill-history to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list-cost-allocation-tag-backfill-history needs a policy

The 'list' verb indicates a retrieval/query operation with no side effects. The reference to 'backfill-history' suggests this returns historical data about cost allocation tag backfills rather than triggering new backfill operations or modifying data. However, confidence is lowered due to the empty description, which prevents full certainty about the tool's actual behavior and scope.

From the tool's definition Tool name contains 'list' and 'history' which are typical Read operations. The name structure suggests querying historical backfill status rather than modifying or executing operations.

Risk signalsBulk/mass operation — affects multiple targets

Questions about list-cost-allocation-tag-backfill-history

What does the list-cost-allocation-tag-backfill-history tool do? +

list-cost-allocation-tag-backfill-history. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-cost-allocation-tag-backfill-history? +

Register the AWS IoT SiteWise MCP Server 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 AWS IoT SiteWise MCP Server. Nothing to install.

What risk level is list-cost-allocation-tag-backfill-history? +

list-cost-allocation-tag-backfill-history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list-cost-allocation-tag-backfill-history? +

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.

How do I block list-cost-allocation-tag-backfill-history completely? +

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.

What MCP server provides list-cost-allocation-tag-backfill-history? +

list-cost-allocation-tag-backfill-history is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.