High Risk →

StartAHORun

Start a workflow run. Args: ctx: MCP context for error reporting workflow_id: ID of the workflow to run role_arn: ARN of the IAM role to use for the run name: Name for the run output_uri: S3 URI for the run outputs parameters: Parameters for the workflow. Parameter...

High parameter count (15 properties)

Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke StartAHORun to trigger processes or run actions in AWS HealthOmics MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

StartAHORun can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

aws-healthomics-mcp-server.yaml
tools:
  StartAHORun:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full AWS HealthOmics MCP Server policy for all 73 tools.

Tool Name StartAHORun
Category Execute
Risk Level High

View all 73 tools →

Agents calling execute-class tools like StartAHORun have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

StartAHORun is one of the high-risk operations in AWS HealthOmics MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the StartAHORun tool do? +

Start a workflow run. Args: ctx: MCP context for error reporting workflow_id: ID of the workflow to run role_arn: ARN of the IAM role to use for the run name: Name for the run output_uri: S3 URI for the run outputs parameters: Parameters for the workflow. Parameter names must match one of the keys in the workflow's parameter template. All non-optional parameters must be present, if they are not provided the workflow run will not start. No other parameter names are allowed. The descriptions of the parameters in the parameter template may provide clues to the type of the parameter. It may be necessary to inspect the workflow definition to determine the appropriate parameter type. workflow_version_name: Optional version name to run storage_type: Storage type (STATIC or DYNAMIC) storage_capacity: Storage capacity in GB (required for STATIC) cache_id: Optional ID of a run cache to use cache_behavior: Optional cache behavior (CACHE_ALWAYS or CACHE_ON_FAILURE) run_group_id: Optional ID of a run group to associate with this run networking_mode: Optional networking mode (RESTRICTED or VPC) configuration_name: Optional configuration name (required when networking_mode is VPC) aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing the run information or error dict. It is categorised as a Execute tool in the AWS HealthOmics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on StartAHORun? +

Add a rule in your Intercept YAML policy under the tools section for StartAHORun. 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.

What risk level is StartAHORun? +

StartAHORun is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit StartAHORun? +

Yes. Add a rate_limit block to the StartAHORun 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.

How do I block StartAHORun completely? +

Set action: deny in the Intercept policy for StartAHORun. 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.

What MCP server provides StartAHORun? +

StartAHORun 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.