Clone a container image to a private ECR repository for HealthOmics use. This tool copies a container image from an upstream registry (Docker Hub, Quay.io, ECR Public) to your private ECR repository with appropriate HealthOmics access permissions. It uses ECR pull-through cache to perform the co...
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call CloneContainerToECR 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 CloneContainerToECR 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:
CloneContainerToECR:
rules:
- action: allowSee the full AWS HealthOmics MCP Server policy for all 73 tools.
Agents calling read-class tools like CloneContainerToECR 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.
Clone a container image to a private ECR repository for HealthOmics use. This tool copies a container image from an upstream registry (Docker Hub, Quay.io, ECR Public) to your private ECR repository with appropriate HealthOmics access permissions. It uses ECR pull-through cache to perform the copy. The tool will: 1. Parse the source image reference (handling Docker Hub shorthand like "ubuntu:latest") 2. Find an existing pull-through cache rule for the source registry 3. Use the pull-through cache to pull the image into ECR 4. Grant HealthOmics access permissions to the repository 5. Return the ECR URI and digest for use in workflows Image reference formats supported: - "ubuntu:latest" -> registry-1.docker.io/library/ubuntu:latest - "myorg/myimage:v1" -> registry-1.docker.io/myorg/myimage:v1 - "quay.io/biocontainers/samtools:1.17" -> quay.io/biocontainers/samtools:1.17 - "public.ecr.aws/lts/ubuntu:22.04" -> public.ecr.aws/lts/ubuntu:22.04 Args: ctx: MCP context for error reporting source_image: Source container image reference target_repository_name: Target ECR repository name (only used if no pull-through cache exists; optional) target_image_tag: Target image tag (optional) aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing: - success: Whether the operation was successful - source_image: Original source image reference - source_registry: Source registry URL - source_digest: Source image digest (if available) - ecr_uri: ECR URI of the cloned image - ecr_digest: ECR image digest - repository_created: Whether a new repository was created - used_pull_through_cache: Whether pull-through cache was used - pull_through_cache_prefix: The pull-through cache prefix used (if any) - healthomics_accessible: Whether HealthOmics can access the image - message: Human-readable status message. 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 CloneContainerToECR. 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.
CloneContainerToECR 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 CloneContainerToECR 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 CloneContainerToECR. 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.
CloneContainerToECR 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.