memory_delete_event
AI agents call memory_delete_event 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.
The 'delete' verb combined with 'event' in a memory/cache system strongly suggests this tool removes cached event data irreversibly. Delete operations fall into the Destructive category because they cannot be undone. High severity is appropriate because deleting events from a cache could cause data loss, break event-driven workflows, or trigger cascading failures in dependent applications.
From the tool's definition Tool name 'memory_delete_event' contains 'delete', which indicates irreversible removal of data. No description provided, but the semantic meaning of 'delete' in a cache/database context implies permanent removal.
Attacks that exploit this kind of access
memory_delete_event. 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 memory_delete_event: 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.
memory_delete_event 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 memory_delete_event 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 memory_delete_event. 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.
memory_delete_event 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.