List pull-through cache rules with HealthOmics usability status. Lists all ECR pull-through cache rules in the current region and evaluates each rule's usability by HealthOmics. A pull-through cache is usable by HealthOmics if: 1. The registry permissions policy grants HealthOmics the required p...
Part of the AWS HealthOmics MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call ListPullThroughCacheRules 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 ListPullThroughCacheRules 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:
ListPullThroughCacheRules:
rules:
- action: allowSee the full AWS HealthOmics MCP Server policy for all 73 tools.
Agents calling read-class tools like ListPullThroughCacheRules 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.
List pull-through cache rules with HealthOmics usability status. Lists all ECR pull-through cache rules in the current region and evaluates each rule's usability by HealthOmics. A pull-through cache is usable by HealthOmics if: 1. The registry permissions policy grants HealthOmics the required permissions 2. A repository creation template exists for the prefix 3. The template grants HealthOmics the required image pull permissions Args: ctx: MCP context for error reporting max_results: Maximum number of results to return (default: 100, max: 1000) next_token: Pagination token from a previous response aws_profile: Optional AWS profile name override aws_region: Optional AWS region override Returns: Dictionary containing: - rules: List of pull-through cache rules with usability status - next_token: Pagination token if more results are available. 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 ListPullThroughCacheRules. 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.
ListPullThroughCacheRules 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 ListPullThroughCacheRules 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 ListPullThroughCacheRules. 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.
ListPullThroughCacheRules 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.