AI agents call gateway_target_delete to permanently remove resources in Amazon ECS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' suffix in the tool name indicates this operation irreversibly removes or destroys a resource. In the context of an AWS ECS server managing containerized deployments, deleting a gateway target could remove routing rules or infrastructure that cannot be easily recovered. This falls under the Destructive category (higher severity than Execute or Write).
From the tool's definition Tool name 'gateway_target_delete' contains the verb 'delete', which indicates irreversible removal of a resource (likely an ECS gateway target). The empty description prevents full certainty but the naming convention strongly suggests a destructive operation.
Documented attack patterns abuse exactly the kind of access gateway_target_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gateway_target_delete:
{
"version": "1",
"default": "deny",
"hide": [
"gateway_target_delete"
]
}gateway_target_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
gateway_target_delete. 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.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for gateway_target_delete: 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 Amazon ECS MCP Server. Nothing to install.
gateway_target_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gateway_target_delete 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.
Set action: deny in the PolicyLayer policy for gateway_target_delete. 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.
gateway_target_delete is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.