getCollectionStats
AI agents call getCollectionStats 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 naming pattern 'get*' is characteristic of read operations that retrieve data without side effects. In the context of AWS IoT SiteWise (a time-series data platform), fetching collection statistics would query existing metrics or counts. Without description text to indicate the tool can modify, delete, or execute external operations, the read category is most appropriate.
From the tool's definition Tool name 'getCollectionStats' indicates retrieval of collection statistics without modification. The empty description prevents full certainty, but the 'get' verb strongly suggests a read-only query operation.
Attacks that exploit this kind of access
getCollectionStats. 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 getCollectionStats: 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.
getCollectionStats 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 getCollectionStats 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 getCollectionStats. 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.
getCollectionStats 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.