Delete a FHIR resource from HealthLake
AI agents call delete_fhir_resource to permanently remove resources in Amazon MQ 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 FHIR resources in AWS HealthLake, a protected health information (PHI) system. Deletion of healthcare records cannot be undone and represents the most severe category. The blast radius is critical as it could permanently remove patient medical records with legal, compliance, and patient safety implications.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a FHIR resource from HealthLake', which irreversibly removes healthcare data.
Attacks that exploit this kind of access
Delete a FHIR resource from HealthLake. It is categorised as a Destructive tool in the Amazon MQ MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon MQ 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 Amazon MQ MCP Server. Nothing to install.
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.
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.
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.
delete_fhir_resource is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.