Delete a data store from AWS HealthImaging.
AI agents call delete_datastore 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 performs an irreversible delete operation on a datastore, which cannot be undone. This is a destructive action that removes data or infrastructure. The high severity reflects the blast radius: accidental deletion of a medical imaging datastore could impact patient data access and breach compliance requirements (HIPAA). Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'delete_datastore' with description 'Delete a data store from AWS HealthImaging' explicitly indicates irreversible deletion of data storage.
Attacks that exploit this kind of access
Delete a data store from AWS HealthImaging. 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_datastore: 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_datastore 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_datastore 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_datastore. 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_datastore 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.