Critical Risk →

delete_fhir_resource

Delete a FHIR resource from HealthLake

How to control delete_fhir_resource ↓

What delete_fhir_resource does on Finch MCP Server

AI agents call delete_fhir_resource to permanently remove resources in Finch MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_fhir_resource needs a policy

This tool performs an irreversible deletion operation on FHIR health resources stored in AWS HealthLake. FHIR resources represent structured healthcare data (patient records, clinical observations, medications, etc.) that cannot be recovered once deleted. Destructive is the correct category as it explicitly removes data without undo capability.

From the tool's definition Tool name is 'delete_fhir_resource' with description 'Delete a FHIR resource from HealthLake'. The verb 'delete' combined with the medical data context (FHIR resources in a healthcare data lake) indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_fhir_resource gives an agent:

How to control delete_fhir_resource

PolicyLayer is an MCP gateway — it sits between your AI agents and Finch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_fhir_resource:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_fhir_resource"
  ]
}

delete_fhir_resource disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Finch MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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 Finch 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 Finch 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 Finch 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 Finch MCP Server MCP server (awslabs.finch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Finch MCP Server tool call.

Start from Finch 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 Finch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.