Validates prerequisites for ECS Express Mode deployment. This tool checks that all required resources exist and are properly configured before deploying an ECS Express Gateway Service. ## Validation Checks: 1. Task Execution Role exists (checks default 'ecsTaskExecutionRole' if not provided) 2....
Part of the Amazon ECS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call validate_ecs_express_mode_prerequisites to retrieve information from Amazon ECS 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 validate_ecs_express_mode_prerequisites 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:
validate_ecs_express_mode_prerequisites:
rules:
- action: allowSee the full Amazon ECS MCP Server policy for all 10 tools.
Agents calling read-class tools like validate_ecs_express_mode_prerequisites 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.
Validates prerequisites for ECS Express Mode deployment. This tool checks that all required resources exist and are properly configured before deploying an ECS Express Gateway Service. ## Validation Checks: 1. Task Execution Role exists (checks default 'ecsTaskExecutionRole' if not provided) 2. Infrastructure Role exists (checks default 'ecsInfrastructureRoleForExpressServices' if not provided) 3. Docker image exists in the specified ECR repository ## Parameters: - Required: image_uri (Full ECR image URI including tag) - Optional: execution_role_arn (ARN of task execution role, defaults to 'ecsTaskExecutionRole') - Optional: infrastructure_role_arn (ARN of infrastructure role, defaults to 'ecsInfrastructureRoleForExpressServices') ## Required IAM Roles: ### Task Execution Role: - Allows ECS tasks to pull images and write logs - Must have trust policy for ecs-tasks.amazonaws.com - Should have AmazonECSTaskExecutionRolePolicy attached ### Infrastructure Role: - Allows ECS to provision infrastructure - Must have trust policy for ecs.amazonaws.com - Should have AmazonECSInfrastructureRoleforExpressGatewayServices attached ## Returns: Dictionary containing: - valid: Boolean indicating if all prerequisites are met - errors: List of error messages if validation fails - warnings: List of warning messages - details: Detailed validation results for each check ## Usage Examples: ``` # Validate with default role names validate_ecs_express_mode_prerequisites( image_uri="123456789012.dkr.ecr.us-west-2.amazonaws.com/my-app:1700000000" ) # Validate with custom role ARNs validate_ecs_express_mode_prerequisites( image_uri="123456789012.dkr.ecr.us-west-2.amazonaws.com/my-app:1700000000", execution_role_arn="arn:aws:iam::123456789012:role/custom-execution-role", infrastructure_role_arn="arn:aws:iam::123456789012:role/custom-infra-role" ) ``` Returns when successful: ``` { "valid": true, "errors": [], "warnings": [], "details": { "execution_role": { "status": "valid", "arn": "arn:aws:iam::123456789012:role/ecsTaskExecutionRole", "name": "ecsTaskExecutionRole", "message": "Task Execution Role is valid" }, "infrastructure_role": { "status": "valid", "arn": "arn:aws:iam::123456789012:role/ecsInfrastructureRoleForExpressServices", "name": "ecsInfrastructureRoleForExpressServices", "message": "Infrastructure Role is valid" }, "image": { "status": "exists", "uri": "123456789012.dkr.ecr.us-west-2.amazonaws.com/my-app:1700000000", "repository": "my-app", "tag": "1700000000", "message": "Image found in ECR" } } } ``` Returns when validation fails: ``` { "valid": false, "errors": [ "Infrastructure Role not found: " "arn:aws:iam::123456789012:role/ecsInfrastructureRoleForExpressServices" ], "warnings": [], "details": { "execution_role": {"status": "valid", ...}, "infrastructure_role": {"status": "not_found", ...}, "image": {"status": "exists", ...} } } ```. It is categorised as a Read tool in the Amazon ECS 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 validate_ecs_express_mode_prerequisites. 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.
validate_ecs_express_mode_prerequisites 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 validate_ecs_express_mode_prerequisites 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 validate_ecs_express_mode_prerequisites. 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.
validate_ecs_express_mode_prerequisites 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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.