DiagnoseAHORunFailure
AI agents call DiagnoseAHORunFailure as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The name suggests a diagnostic/read operation (analyzing failure information), but the description is empty so the actual behavior is unknown. 'Diagnose' typically implies reading/querying failure data, which would be a Read category. However, without any description, confidence is low. Defaulting to Read-like behavior based on naming convention, but categorizing as Other due to insufficient information.
From the tool's definition Tool name 'DiagnoseAHORunFailure' and empty description provide no detail about what the tool does beyond suggesting it diagnoses a run failure.
Attacks that exploit this kind of access
DiagnoseAHORunFailure. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for DiagnoseAHORunFailure: 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.
DiagnoseAHORunFailure is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the DiagnoseAHORunFailure 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 DiagnoseAHORunFailure. 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.
DiagnoseAHORunFailure 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.