Critical Risk →

delete_ecs_infrastructure

Deletes ECS infrastructure created by the ECS MCP Server. WARNING: This tool is not intended for production usage and is best suited for tearing down prototyped work done with the ECS MCP Server. This tool attempts to identify and delete CloudFormation stacks based on the provided app name and ...

Part of the Amazon ECS MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call delete_ecs_infrastructure to permanently remove or destroy resources in Amazon ECS MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_ecs_infrastructure in a loop, permanently destroying resources in Amazon ECS MCP Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

amazon-ecs-mcp-server.yaml
tools:
  delete_ecs_infrastructure:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

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

Tool Name delete_ecs_infrastructure
Category Destructive
Risk Level Critical

View all 10 tools →

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

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

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

What does the delete_ecs_infrastructure tool do? +

Deletes ECS infrastructure created by the ECS MCP Server. WARNING: This tool is not intended for production usage and is best suited for tearing down prototyped work done with the ECS MCP Server. This tool attempts to identify and delete CloudFormation stacks based on the provided app name and template files. It will scan the user's CloudFormation stacks, using the app name as a heuristic, and identify if the templates match the files provided in the input. It will only attempt to delete stacks if they are found and match the provided templates. USAGE INSTRUCTIONS: 1. Provide the name of your application 2. Provide paths to the ECR and ECS CloudFormation template files - Templates will be compared to ensure they match the deployed stacks 3. The tool will attempt to delete the stacks in the correct order (ECS first, then ECR) IMPORTANT: - This is a best-effort deletion - If a stack is in a transitional state (e.g., CREATE_IN_PROGRESS), it will be skipped - You may need to manually delete resources if the deletion fails Parameters: app_name: Name of the application ecr_template_path: Path to the ECR CloudFormation template file ecs_template_path: Path to the ECS CloudFormation template file Returns: Dictionary containing deletion results and guidance. It is categorised as a Destructive tool in the Amazon ECS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_ecs_infrastructure? +

Add a rule in your Intercept YAML policy under the tools section for delete_ecs_infrastructure. 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 delete_ecs_infrastructure? +

delete_ecs_infrastructure is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_ecs_infrastructure? +

Yes. Add a rate_limit block to the delete_ecs_infrastructure 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 delete_ecs_infrastructure completely? +

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

delete_ecs_infrastructure 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.