Update an existing FHIR resource in HealthLake
AI agents use update_fhir_resource to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
This tool creates or modifies data (FHIR resources in AWS HealthLake) in a reversible manner. While updates to healthcare data carry high severity due to potential patient safety and compliance implications, the action itself is not destructive (data can be corrected) or financial. The Write category applies as the primary risk, with high severity reflecting the sensitive nature of health records.
From the tool's definition Tool name contains 'update' and description states 'Update an existing FHIR resource in HealthLake', which modifies healthcare data reversibly.
Attacks that exploit this kind of access
Update an existing FHIR resource in HealthLake. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for update_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 IoT SiteWise MCP Server. Nothing to install.
update_fhir_resource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_fhir_resource is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.