LintAHOWorkflowDefinition
AI agents call LintAHOWorkflowDefinition as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The name suggests this tool validates or lints a workflow definition (static analysis), which would be a Read-like operation with no side effects. However, the description is completely empty, making it impossible to confirm. Lint operations typically only analyze and report issues without modifying data. Confidence is low due to missing description.
From the tool's definition Tool description is empty; tool name 'LintAHOWorkflowDefinition' suggests a linting/validation operation on a workflow definition
Attacks that exploit this kind of access
LintAHOWorkflowDefinition. 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 LintAHOWorkflowDefinition: 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.
LintAHOWorkflowDefinition 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 LintAHOWorkflowDefinition 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 LintAHOWorkflowDefinition. 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.
LintAHOWorkflowDefinition 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.