list-billing-views
AI agents call list-billing-views 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.
The tool appears to query or retrieve billing view configurations for display/inspection purposes. No modification, deletion, or external operation is implied by the name. While billing data access can be sensitive, the Read operation itself presents low immediate risk—misuse would involve information disclosure rather than state change.
From the tool's definition Tool name 'list-billing-views' indicates it retrieves or enumerates billing view objects without modifying them. The 'list-' prefix is consistent with Read operations (list, get, fetch). Description is empty, which reduces confidence slightly.
Attacks that exploit this kind of access
list-billing-views. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for list-billing-views: 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.
list-billing-views 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-billing-views 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-billing-views. 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-billing-views 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.