delete-replication-group
AI agents call delete-replication-group 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.
This tool irreversibly deletes an ElastiCache or MemoryDB replication group, which cannot be undone without restoration from backups. Deletion of replication infrastructure is a destructive action with significant blast radius if invoked unintentionally by an AI agent. Although the description is empty, the tool name itself provides sufficient evidence of destructive intent.
From the tool's definition Tool name 'delete-replication-group' indicates deletion of a replication group resource in AWS ElastiCache/MemoryDB. The 'delete-' prefix is a strong signal of irreversible data/resource destruction.
Attacks that exploit this kind of access
delete-replication-group. 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-replication-group: 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-replication-group 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-replication-group 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-replication-group. 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-replication-group 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.