Deletes a Timestream for InfluxDB DB instance by the instance-identifier
AI agents call DeleteDbInstance 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 destroys an entire database instance and all associated data. Deletion is irreversible and represents the maximum blast radius for data loss. Even with backups, the immediate effect is data destruction. This is categorically Destructive rather than Write, as it removes data permanently rather than modifying it reversibly.
From the tool's definition Tool name is 'DeleteDbInstance' and description explicitly states it 'Deletes a Timestream for InfluxDB DB instance'. The verb 'Deletes' combined with the scope (entire DB instance) indicates an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Deletes a Timestream for InfluxDB DB instance by the instance-identifier. 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 DeleteDbInstance: 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.
DeleteDbInstance 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 DeleteDbInstance 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 DeleteDbInstance. 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.
DeleteDbInstance 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.