This record as markdown: /tools/aws/delete-datastore.md
What delete_datastore does on AWS
AI agents call delete_datastore to permanently remove resources in AWS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_datastore is rated Critical
Deletion of a data store is an irreversible operation that cannot be undone. This falls squarely into the Destructive category as it permanently removes data. The severity is high because deleting a data store in a healthcare imaging system could result in loss of critical medical data, affecting patient care and compliance.
From the tool's definition Tool name is 'delete_datastore' and description states 'Delete a data store from AWS HealthImaging'. The verb 'delete' combined with 'data store' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_datastore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_datastore, this is the rule to start with:
delete_datastore is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every delete_datastore call is checked against it from then on.
Questions about delete_datastore
Delete a data store from AWS HealthImaging. It is categorised as a Destructive tool in the AWS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS 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. 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 MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
Across the catalogue