generate_cost_report
AI agents call generate_cost_report as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The name suggests generating a cost report, which is a read/reporting action and does not inherently move money or commit financial obligations. However, the description is empty, so there is uncertainty. 'Generate' implies producing a report (Read), but in some contexts cost reporting tools can trigger billing operations.
From the tool's definition Tool name is 'generate_cost_report'; description is empty and uninformative.
Attacks that exploit this kind of access
generate_cost_report. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for generate_cost_report: 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.
generate_cost_report is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the generate_cost_report 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 generate_cost_report. 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.
generate_cost_report 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.