Create a container registry map for HealthOmics workflows. Creates a container registry map file that can be used when creating HealthOmics workflows. Registry mappings allow workflows to use container images from upstream registries (Docker Hub, Quay.io, ECR Public) without modifying the workfl...
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use CreateContainerRegistryMap to create or modify resources in AWS HealthOmics MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call CreateContainerRegistryMap repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS HealthOmics MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
CreateContainerRegistryMap:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS HealthOmics MCP Server policy for all 73 tools.
Agents calling write-class tools like CreateContainerRegistryMap have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a container registry map for HealthOmics workflows. Creates a container registry map file that can be used when creating HealthOmics workflows. Registry mappings allow workflows to use container images from upstream registries (Docker Hub, Quay.io, ECR Public) without modifying the workflow definition. The mappings redirect container pulls to your private ECR pull-through caches. By default, this tool discovers all HealthOmics-usable pull-through cache rules in your ECR registry and creates mappings for them. You can also provide additional registry mappings or specific image mappings for container overrides. Args: ctx: MCP context for error reporting ecr_account_id: AWS account ID for ECR repositories. If not provided, uses the current AWS account. ecr_region: AWS region for ECR repositories. If not provided, uses the current configured region. include_pull_through_caches: If true, automatically discovers HealthOmics-usable ECR pull-through cache rules and creates registry mappings for them. additional_registry_mappings: Additional registry mappings to include beyond discovered pull-through caches. Each mapping should have 'upstreamRegistryUrl' and 'ecrRepositoryPrefix' keys. image_mappings: List of specific image mappings for container overrides. Each mapping should have 'sourceImage' and 'destinationImage' keys. These take precedence over registry mappings. output_format: Output format - 'json' for raw JSON string, 'dict' for dictionary. aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing: - success: Whether the operation was successful - account_id: AWS account ID used - region: AWS region used - discovered_healthomics_usable_caches: Number of HealthOmics-usable caches found - container_registry_map: The generated container registry map - json_output: Pretty-printed JSON string ready for use - usage_hint: Instructions for using the generated map. It is categorised as a Write tool in the AWS HealthOmics MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for CreateContainerRegistryMap. 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.
CreateContainerRegistryMap is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the CreateContainerRegistryMap 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 CreateContainerRegistryMap. 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.
CreateContainerRegistryMap 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.