build_and_push_image_to_ecr

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke build_and_push_image_to_ecr to trigger processes or run actions in Amazon ECS MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON BUILD_AND_PUSH_IMAGE_TO_ECR

build_and_push_image_to_ecr can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

amazon-ecs-mcp-server.yaml

tools:
  build_and_push_image_to_ecr:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Amazon ECS MCP Server policy for all 10 tools.

// DETAILS

Tool Name build_and_push_image_to_ecr

Category Execute

MCP Server Amazon ECS MCP Server MCP Server

Risk Level High

// MORE AMAZON ECS MCP SERVER TOOLS

Destructive delete_app Destructive delete_ecs_infrastructure Execute containerize_app Execute ecs_resource_management Execute ecs_troubleshooting_tool Execute wait_for_service_ready Write create_ecs_infrastructure Read get_deployment_status

View all 10 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like build_and_push_image_to_ecr have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

build_and_push_image_to_ecr is one of the high-risk operations in Amazon ECS MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the build_and_push_image_to_ecr tool do? +

Creates ECR infrastructure and builds/pushes a Docker image to ECR. This tool automates the complete ECR setup and image deployment process: 1. Creates ECR repository via CloudFormation 2. Creates IAM role with ECR push/pull permissions 3. Builds Docker image from your application 4. Pushes image to ECR ## Parameters: - Required: app_name (Application name, 1-20 chars, lowercase letters/digits/hyphens only) - Required: app_path (Path to application directory with Dockerfile) - Optional: tag (Image tag, defaults to epoch timestamp) ## Prerequisites: - Docker installed and running locally - Dockerfile exists in the application directory - AWS credentials configured with appropriate permissions ## Returns: Dictionary containing: - repository_uri: ECR repository URI - image_tag: The tag of the pushed image - full_image_uri: Complete image URI with tag (use this for deployment) - ecr_push_pull_role_arn: ARN of the IAM role created for ECR access - stack_name: Name of the CloudFormation stack created ## Usage Examples: ``` # Build and push with auto-generated tag build_and_push_image_to_ecr( app_name="my-app", app_path="/home/user/my-flask-app" ) # Build and push with specific tag build_and_push_image_to_ecr( app_name="my-app", app_path="/home/user/my-flask-app", tag="v1.0.0" ) ``` Returns: ``` { "repository_uri": "123456789012.dkr.ecr.us-west-2.amazonaws.com/my-app-repo", "image_tag": "1700000000", "full_image_uri": "123456789012.dkr.ecr.us-west-2.amazonaws.com/my-app-repo:1700000000", "ecr_push_pull_role_arn": "arn:aws:iam::123456789012:role/my-app-ecr-push-pull-role", "stack_name": "my-app-ecr-infrastructure" } ```. It is categorised as a Execute tool in the Amazon ECS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_and_push_image_to_ecr? +

Add a rule in your Intercept YAML policy under the tools section for build_and_push_image_to_ecr. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon ECS MCP Server MCP server.

What risk level is build_and_push_image_to_ecr? +

build_and_push_image_to_ecr is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_and_push_image_to_ecr? +

Yes. Add a rate_limit block to the build_and_push_image_to_ecr 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.

How do I block build_and_push_image_to_ecr completely? +

Set action: deny in the Intercept policy for build_and_push_image_to_ecr. 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.

What MCP server provides build_and_push_image_to_ecr? +

build_and_push_image_to_ecr is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

build_and_push_image_to_ecr

Let agents act without letting them run wild.