Check if a container image is available in ECR and accessible by HealthOmics. Queries ECR to determine if a specific container image exists in a repository and whether HealthOmics has the required permissions to pull the image. For pull-through cache repositories, indicates that the image may be...
Single-target operation
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call CheckContainerAvailability 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 CheckContainerAvailability 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:
CheckContainerAvailability:
rules:
- action: allowSee the full AWS HealthOmics MCP Server policy for all 73 tools.
Agents calling read-class tools like CheckContainerAvailability 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.
Check if a container image is available in ECR and accessible by HealthOmics. Queries ECR to determine if a specific container image exists in a repository and whether HealthOmics has the required permissions to pull the image. For pull-through cache repositories, indicates that the image may be pulled on first access even if not currently cached. When initiate_pull_through is True and the image is not found in a pull-through cache repository that is accessible to HealthOmics, this function will attempt to initiate the pull-through using ECR's batch_get_image API call. This triggers ECR to pull the image from the upstream registry and cache it locally. Args: ctx: MCP context for error reporting repository_name: ECR repository name (e.g., "my-repo" or "docker-hub/library/ubuntu") image_tag: Image tag to check (default: "latest") image_digest: Image digest (sha256:...) - if provided, takes precedence over tag initiate_pull_through: If True, attempt to initiate pull-through cache for missing images in accessible pull-through cache repositories aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing: - available: Whether the image is available - image: Image details if available (digest, size, push timestamp) - repository_exists: Whether the repository exists - is_pull_through_cache: Whether this is a pull-through cache repository - healthomics_accessible: Whether HealthOmics can access the image - missing_permissions: List of missing ECR permissions for HealthOmics - message: Human-readable status message - pull_through_initiated: Whether a pull-through was initiated - pull_through_initiation_message: Message about pull-through initiation result. 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 CheckContainerAvailability. 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.
CheckContainerAvailability 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 CheckContainerAvailability 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 CheckContainerAvailability. 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.
CheckContainerAvailability 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.