gateway_delete
AI agents call gateway_delete 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.
Although the description is empty and confidence cannot be higher, the tool name itself contains 'delete'—a strong signal of destructive action. In the context of an ElastiCache/MemoryDB gateway, a delete operation would irreversibly remove a gateway resource or its configuration.
From the tool's definition Tool name 'gateway_delete' contains 'delete', which is explicitly listed in the destructive category criteria. The verb 'delete' indicates irreversible data removal or resource destruction.
Attacks that exploit this kind of access
gateway_delete. 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 gateway_delete: 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.
gateway_delete 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 gateway_delete 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 gateway_delete. 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.
gateway_delete 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.