delete-cache-cluster
AI agents call delete-cache-cluster 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.
Deleting a cache cluster destroys the entire cluster and its data. This is an irreversible action with significant blast radius—loss of cached data, service interruption, and potential data loss if the cluster is the sole source of data. The empty description prevents more detailed analysis, but the name alone is sufficiently clear. This merits the Destructive category and critical severity.
From the tool's definition Tool name 'delete-cache-cluster' contains the verb 'delete', which is explicitly listed as a destructive action. The deletion of a cache cluster is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
delete-cache-cluster. 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-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 Awslabs Valkey. Nothing to install.
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.
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.
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.
delete-cache-cluster 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.