Lint WDL or CWL workflow definitions and return validation findings. This tool validates workflow definitions using appropriate linting tools: - WDL workflows: Uses miniwdl package for parsing and validation - CWL workflows: Uses cwltool package for parsing and validation The tool checks for: -...
Accepts file system path (filename)
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call LintAHOWorkflowDefinition to retrieve information from AWS HealthOmics MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though LintAHOWorkflowDefinition only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
LintAHOWorkflowDefinition:
rules:
- action: allowSee the full AWS HealthOmics MCP Server policy for all 73 tools.
Agents calling read-class tools like LintAHOWorkflowDefinition have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Lint WDL or CWL workflow definitions and return validation findings. This tool validates workflow definitions using appropriate linting tools: - WDL workflows: Uses miniwdl package for parsing and validation - CWL workflows: Uses cwltool package for parsing and validation The tool checks for: - Syntax errors and parsing issues - Missing required fields (inputs, outputs, steps) - Runtime requirements for tasks - Common workflow structure issues Args: ctx: MCP context for error reporting workflow_content: The workflow definition content to lint. Accepts inline content, a local file path, or an S3 URI (s3://bucket/key). workflow_format: The workflow format ('wdl' or 'cwl') filename: Optional filename for context in error messages Returns: Dictionary containing: - status: 'success' or 'error' - format: The workflow format that was linted - filename: The filename that was processed (optional) - linter: Name of the linting tool used - raw_output: Raw output from the linter command execution. It is categorised as a Read tool in the AWS HealthOmics MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for LintAHOWorkflowDefinition. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS HealthOmics MCP Server MCP server.
LintAHOWorkflowDefinition 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 LintAHOWorkflowDefinition rule in your Intercept 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 Intercept 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 HealthOmics MCP Server MCP server (awslabs.aws-healthomics-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.