Create a pull-through cache rule configured for HealthOmics. Creates an ECR pull-through cache rule for the specified upstream registry and configures the necessary permissions for HealthOmics to use it. This includes: 1. Creating the pull-through cache rule 2. Updating the registry permissions ...
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use CreatePullThroughCacheForHealthOmics 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 CreatePullThroughCacheForHealthOmics 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:
CreatePullThroughCacheForHealthOmics:
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 CreatePullThroughCacheForHealthOmics 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 pull-through cache rule configured for HealthOmics. Creates an ECR pull-through cache rule for the specified upstream registry and configures the necessary permissions for HealthOmics to use it. This includes: 1. Creating the pull-through cache rule 2. Updating the registry permissions policy to allow HealthOmics to create repositories and import images 3. Creating a repository creation template that grants HealthOmics the required permissions to pull images Args: ctx: MCP context for error reporting upstream_registry: Upstream registry type (docker-hub, quay, or ecr-public) ecr_repository_prefix: ECR repository prefix (defaults to registry type name) credential_arn: Secrets Manager ARN for registry credentials (required for docker-hub, optional for others) aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing: - success: Whether the operation was successful - rule: Created pull-through cache rule details - registry_policy_updated: Whether the registry policy was updated - repository_template_created: Whether the repository template was created - message: Human-readable status message. 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 CreatePullThroughCacheForHealthOmics. 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.
CreatePullThroughCacheForHealthOmics 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 CreatePullThroughCacheForHealthOmics 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 CreatePullThroughCacheForHealthOmics. 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.
CreatePullThroughCacheForHealthOmics 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.