Delete a data store from AWS HealthImaging.
AI agents call delete_datastore to permanently remove resources in AWS Step Functions Tool 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 AWS HealthImaging datastores. Once deleted, the datastore and its contents cannot be recovered without backups. This is a destructive action that could result in permanent loss of medical imaging data. The severity is high because deletion of healthcare data repositories can impact patient care and compliance, though financial impact is not directly mentioned.
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 the description explicitly indicates irreversible removal of data storage.
Documented attack patterns abuse exactly the kind of access delete_datastore gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Step Functions Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_datastore:
{
"version": "1",
"default": "deny",
"hide": [
"delete_datastore"
]
} delete_datastore disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a data store from AWS HealthImaging. It is categorised as a Destructive tool in the AWS Step Functions Tool MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Step Functions Tool 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 Step Functions Tool 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 Step Functions Tool MCP Server MCP server (awslabs.stepfunctions-tool-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Step Functions Tool MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Step Functions Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.