cost-comparison
AI agents call cost-comparison 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.
While the name contains 'cost', it most likely performs read-only cost analysis or reporting (comparing existing cost metrics). No evidence suggests money movement, resource deletion, or code execution. The empty description reduces confidence from high to medium-low; if this performs write operations on cost allocations or budget modifications, the category would shift to Write.
From the tool's definition Tool name 'cost-comparison' suggests comparing cost data, and the AWS IoT SiteWise context indicates financial metric analysis. The empty description limits certainty, but the name pattern implies data retrieval or analysis rather than financial transactions.
Attacks that exploit this kind of access
cost-comparison. 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 cost-comparison: 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.
cost-comparison 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 cost-comparison 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 cost-comparison. 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.
cost-comparison 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.