High Risk →

StartAHOReadSetExportJob

Start a read set export job to export read sets from a sequence store to S3. Args: ctx: MCP context for error reporting sequence_store_id: The ID of the sequence store destination_s3_uri: S3 URI for the export destination role_arn: IAM role ARN for the export job read_set_ids...

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

AI agents invoke StartAHOReadSetExportJob 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.

StartAHOReadSetExportJob 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:
  StartAHOReadSetExportJob:
    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 StartAHOReadSetExportJob
Category Execute
Risk Level High

View all 73 tools →

Agents calling execute-class tools like StartAHOReadSetExportJob 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.

StartAHOReadSetExportJob 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 StartAHOReadSetExportJob tool do? +

Start a read set export job to export read sets from a sequence store to S3. Args: ctx: MCP context for error reporting sequence_store_id: The ID of the sequence store destination_s3_uri: S3 URI for the export destination role_arn: IAM role ARN for the export job read_set_ids: List of read set IDs to export aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing the export job information. 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 StartAHOReadSetExportJob? +

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

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

Can I rate-limit StartAHOReadSetExportJob? +

Yes. Add a rate_limit block to the StartAHOReadSetExportJob 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 StartAHOReadSetExportJob completely? +

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

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