delete_series_by_uid
AI agents call delete_series_by_uid 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 tool explicitly performs a delete operation on series identified by UID. Deletion is inherently irreversible and cannot be undone without external backups. Even without a detailed description, the naming convention is a reliable indicator of destructive intent. This poses significant risk if an AI agent misuses it, as it could permanently remove data without recovery options.
From the tool's definition Tool name 'delete_series_by_uid' contains 'delete' which indicates irreversible removal of data. The lack of description reduces certainty slightly, but the verb 'delete' combined with 'series' (likely time-series data in an ElastiCache/MemoryDB context)…
Attacks that exploit this kind of access
delete_series_by_uid. 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_series_by_uid: 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_series_by_uid 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_series_by_uid 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_series_by_uid. 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_series_by_uid 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.