delete_ecs_infrastructure

delete_ecs_infrastructure

Server AWS HealthOmics MCP Server awslabs.aws-healthomics-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_ecs_infrastructure does on AWS HealthOmics MCP Server

AI agents call delete_ecs_infrastructure to permanently remove resources in AWS HealthOmics MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_ecs_infrastructure needs a policy

The 'delete' prefix paired with infrastructure component deletion places this in the Destructive category as the highest severity. ECS infrastructure deletion is irreversible and has broad blast radius affecting running containerized services, task definitions, and cluster configurations. Even without explicit confirmation language, infrastructure deletion tools pose critical risk.

From the tool's definition Tool name explicitly contains 'delete' combined with 'ecs_infrastructure', indicating irreversible removal of AWS ECS resources. No description provided to clarify scope, but the naming convention strongly suggests data/infrastructure deletion.

Questions about delete_ecs_infrastructure

What does the delete_ecs_infrastructure tool do? +

delete_ecs_infrastructure. It is categorised as a Destructive tool in the AWS HealthOmics 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? +

Register the AWS HealthOmics MCP Server MCP server in PolicyLayer and add a rule for delete_ecs_infrastructure: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS HealthOmics MCP Server. Nothing to install.

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 PolicyLayer 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 PolicyLayer 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 AWS HealthOmics MCP Server MCP server (awslabs.aws-healthomics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.