Delete a data store from AWS HealthImaging.
AI agents call delete_datastore to permanently remove resources in AWS HealthOmics MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on a data store, which cannot be undone. Deletion of healthcare data stores could result in permanent loss of medical imaging data and related records. While not directly moving money (Financial), the irreversible nature of deletion makes this Destructive rather than Write.
From the tool's definition Tool name is 'delete_datastore' and description states 'Delete a data store from AWS HealthImaging.' The use of 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a data store from AWS HealthImaging. It is categorised as a Destructive tool in the AWS HealthOmics MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS HealthOmics MCP Server 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 AWS HealthOmics MCP Server. 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 AWS HealthOmics MCP Server MCP server (awslabs.aws-healthomics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.