get_scan_findings
AI agents call get_scan_findings 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 pattern 'get_scan_findings' follows standard read semantics—retrieving existing scan findings from AWS IoT SiteWise without side effects. No creation, modification, deletion, or execution of arbitrary code is implied. The absence of descriptive text reduces confidence slightly, but the naming convention is a reliable indicator of read-only behavior in AWS API patterns.
From the tool's definition Tool name 'get_scan_findings' indicates retrieval of scan results without modification. The empty description prevents higher confidence, but the 'get_' prefix strongly suggests a query/read operation.
Attacks that exploit this kind of access
get_scan_findings. 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 get_scan_findings: 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.
get_scan_findings 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 get_scan_findings 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 get_scan_findings. 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.
get_scan_findings 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.