ListAHOWorkflowVersions
AI agents call ListAHOWorkflowVersions 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 convention 'List' combined with 'AHOWorkflowVersions' indicates this tool retrieves or enumerates workflow version data without modifying state. List operations are classified as Read category. Confidence is slightly reduced due to the empty description, but the verb 'List' is a reliable indicator of retrieval-only behavior with no side effects.
From the tool's definition Tool name 'ListAHOWorkflowVersions' indicates a list/query operation. The 'List' prefix strongly suggests data retrieval. Description is empty, limiting full certainty.
Attacks that exploit this kind of access
ListAHOWorkflowVersions. 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 ListAHOWorkflowVersions: 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.
ListAHOWorkflowVersions 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 ListAHOWorkflowVersions 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 ListAHOWorkflowVersions. 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.
ListAHOWorkflowVersions 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.