list_sub_check_results
AI agents call list_sub_check_results 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 name strongly suggests querying or enumerating check results (likely subscription or sub-component checks in the AWS IoT SiteWise context). Listing operations retrieve data without side effects. However, confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about the actual implementation and scope of what 'sub_check_results' refers to.
From the tool's definition Tool name 'list_sub_check_results' indicates a retrieval/listing operation with no modification semantics. The verb 'list' is a canonical Read operation pattern.
Attacks that exploit this kind of access
list_sub_check_results. 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_sub_check_results: 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_sub_check_results 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_sub_check_results 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_sub_check_results. 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_sub_check_results 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.