delete_ecs_infrastructure
AI agents call delete_ecs_infrastructure to permanently remove resources in Awslabs Valkey — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name clearly indicates deletion ('delete_ecs_infrastructure'), which falls under the Destructive category as it irreversibly removes infrastructure resources and cannot be undone. This represents the most severe category applicable.
From the tool's definition Tool name is 'delete_ecs_infrastructure' which explicitly indicates deletion of AWS ECS infrastructure resources. The word 'delete' signals irreversible removal of infrastructure.
Attacks that exploit this kind of access
delete_ecs_infrastructure. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Valkey 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 Awslabs Valkey. Nothing to install.
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.
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.
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.
delete_ecs_infrastructure is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.