LintAHOWorkflowDefinition
AI agents call LintAHOWorkflowDefinition as a supporting operation in Amazon MQ MCP Server workflows.
The name suggests a linting operation (static analysis/validation) on a workflow definition, which would typically be a read-only operation with no side effects. However, the description is empty, so confidence is low.
From the tool's definition Tool name 'LintAHOWorkflowDefinition' and empty description provide no clear indication of side effects
Attacks that exploit this kind of access
LintAHOWorkflowDefinition. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ 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 Amazon MQ 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 Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.