Critical Risk →

delete-cache-cluster

delete-cache-cluster

How to control delete-cache-cluster ↓

What delete-cache-cluster does on Amazon ECS MCP Server

AI agents call delete-cache-cluster 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.

Critical Risk

Why delete-cache-cluster needs a policy

The tool name clearly indicates deletion of a cache cluster, which is an irreversible operation that cannot be undone. While the description is empty (lowering confidence slightly), the explicit 'delete' verb in the tool name makes the destructive nature unambiguous.

From the tool's definition Tool name is 'delete-cache-cluster' which explicitly indicates deletion of a cache cluster resource. The verb 'delete' combined with 'cache-cluster' indicates irreversible removal of infrastructure.

Documented attack patterns abuse exactly the kind of access delete-cache-cluster gives an agent:

How to control delete-cache-cluster

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-cache-cluster:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-cache-cluster"
  ]
}

delete-cache-cluster disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Amazon ECS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete-cache-cluster

What does the delete-cache-cluster tool do? +

delete-cache-cluster. 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-cache-cluster? +

Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for delete-cache-cluster: 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.

What risk level is delete-cache-cluster? +

delete-cache-cluster 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-cache-cluster? +

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

Set action: deny in the PolicyLayer policy for delete-cache-cluster. 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-cache-cluster? +

delete-cache-cluster 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.

Enforce policy on every Amazon ECS MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.