Function Health

Function's documentation says it does not. The docs state that individual lab test values or specific results, biomarker IDs, email addresses and detailed personal health information are never sent through the connector, and that it retrieves summary-level data only — counts of in-range and out-of-range biomarkers, category names, and nutrition goals. We could not independently verify this, because the endpoint is auth-gated.

No write path exists in the published surface. All three tools read, all three OAuth scopes begin with read, and Function's documentation states the connector has read-only access and cannot modify your information. It also publishes readOnlyHint true and destructiveHint false. We could not read those annotations off the wire ourselves, so they are Function's claim rather than our observation.

Not uniformly, and Function says so directly. Its privacy policy states Function may operate as a HIPAA business associate but that HIPAA does not apply to all personal information it processes. For a consumer membership bought directly, the data is generally consumer health data under state law rather than HIPAA-protected. Function publishes a separate Consumer Health Data Privacy Policy covering that path.

Three named read scopes, one per tool. The server's RFC 9728 descriptor advertised read:health_summary, read:biomarkers and read:action_plan on 2026-08-22. Each maps to one tool, so the consent screen genuinely separates the three surfaces. No scope grants writing anything, and the identity-only scopes on Function's Auth0 tenant are separate from these three.

A Function membership with completed lab results, and a paid Claude plan. Function's documentation lists both as prerequisites and notes that connectors require a Pro or Max subscription. If your lab results are still being processed the tools return nothing, which Function documents as a distinct troubleshooting case rather than an error condition.

Because an edge layer blocks the request before authentication is evaluated. On 2026-08-22 the endpoint returned a generic Google 403 HTML page to an anonymous handshake, with no www-authenticate header, and returned the same body to a plain GET. That is a WAF block rather than an auth challenge, so it says nothing about the server's auth posture.

One parameter deserves attention. The nutrition tool accepts a free-text context parameter for personalization, which Function's docs describe only as additional context. Everything else is a filter over data you already hold. Treat that field as the one place where text you supply, rather than summary counts, leaves the conversation.

Yes, from either side independently. Function's documentation states you can revoke authorization from your Function account settings and separately disconnect or remove the connector from Claude at any time. It also notes you may request data deletion under applicable privacy laws. Function recommends disconnecting when you are not actively using the connector.