GetSecurityFindings
AI agents call GetSecurityFindings 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 security findings (audit logs, vulnerability scans, compliance data) without modifying them. This is a Read operation. Severity is medium because unauthorized access to security findings could expose sensitive compliance and vulnerability information, but the tool itself performs no destructive or financial actions.
From the tool's definition Tool name 'GetSecurityFindings' indicates retrieval of security audit/scan results. The verb 'Get' aligns with read-only query operations. No description provided to confirm write, execute, or destructive capabilities.
Attacks that exploit this kind of access
GetSecurityFindings. 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 GetSecurityFindings: 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.
GetSecurityFindings 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 GetSecurityFindings 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 GetSecurityFindings. 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.
GetSecurityFindings 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.