AI agents call delete-serverless-cache 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' verb in the tool name indicates an irreversible action that removes a serverless cache resource. Even without a detailed description, deletion tools are inherently destructive because they cannot be undone. The high severity reflects that deleting a cache could disrupt application performance and data availability.
From the tool's definition Tool name 'delete-serverless-cache' contains the verb 'delete', which indicates irreversible removal of data. The tool description is empty, but the name alone strongly suggests deletion of a cache resource.
Documented attack patterns abuse exactly the kind of access delete-serverless-cache 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 delete-serverless-cache:
{
"version": "1",
"default": "deny",
"hide": [
"delete-serverless-cache"
]
}delete-serverless-cache 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.
delete-serverless-cache. 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 delete-serverless-cache: 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.
delete-serverless-cache 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-serverless-cache 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-serverless-cache. 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-serverless-cache 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.