CreateAHOWorkflow
AI agents use CreateAHOWorkflow to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
The 'Create' prefix indicates a Write operation that establishes new workflow resources in AWS IoT SiteWise. Given the AWS context and workflow creation semantics, this likely creates or configures assets, models, or automation workflows that modify system state. Classified as Write rather than Execute because workflow creation typically commits configuration changes reversibly (workflows can be updated or deleted).
From the tool's definition Tool name 'CreateAHOWorkflow' indicates creation of a workflow resource. The description is empty, limiting direct evidence of scope and effects.
Attacks that exploit this kind of access
CreateAHOWorkflow. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for CreateAHOWorkflow: 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.
CreateAHOWorkflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the CreateAHOWorkflow 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 CreateAHOWorkflow. 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.
CreateAHOWorkflow 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.