delete-serverless-cache
AI agents call delete-serverless-cache 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 performs a destructive operation on cloud infrastructure. Deleting a serverless cache is irreversible and results in loss of data and resource availability. While the description is empty (lowering confidence slightly), the explicit 'delete' action name and resource type make the destructive nature clear.
From the tool's definition Tool name 'delete-serverless-cache' indicates permanent removal of a serverless cache resource. No description provided, but the delete_ prefix combined with 'serverless-cache' (an AWS ElastiCache/MemoryDB resource) strongly suggests irreversible deletion.
Attacks that exploit this kind of access
delete-serverless-cache. 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-serverless-cache: 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-serverless-cache 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-serverless-cache 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-serverless-cache. 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-serverless-cache 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.