delete_fhir_resource

Delete a FHIR resource from HealthLake

Server AWS HealthOmics MCP Server awslabs.aws-healthomics-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_fhir_resource does on AWS HealthOmics MCP Server

AI agents call delete_fhir_resource 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.

Why delete_fhir_resource needs a policy

Deletion of healthcare data is irreversible and represents the highest-severity operation class. FHIR resources in HealthLake may contain patient records, clinical observations, or other sensitive medical information. Accidental or malicious deletion via an AI agent could permanently destroy critical healthcare data with no undo mechanism, affecting patient care and compliance.

From the tool's definition Tool is named 'delete_fhir_resource' with description 'Delete a FHIR resource from HealthLake'. The verb 'delete' is explicit and unambiguous; FHIR resources in HealthLake are healthcare data that, once deleted, cannot be recovered without restore procedures.

Questions about delete_fhir_resource

What does the delete_fhir_resource tool do? +

Delete a FHIR resource from HealthLake. 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.

How do I enforce a policy on delete_fhir_resource? +

Register the AWS HealthOmics MCP Server MCP server in PolicyLayer and add a rule for delete_fhir_resource: 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.

What risk level is delete_fhir_resource? +

delete_fhir_resource is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_fhir_resource? +

Yes. Add a rate_limit block to the delete_fhir_resource 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.

How do I block delete_fhir_resource completely? +

Set action: deny in the PolicyLayer policy for delete_fhir_resource. 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.

What MCP server provides delete_fhir_resource? +

delete_fhir_resource 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.