AI agents call get_document_reference to retrieve information from Healow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves clinical document metadata (DocumentReference) from a FHIR API without modifying, deleting, or executing any operations. It is a read-only query operation on healthcare data. While the data is sensitive (clinical documents), the tool itself performs no destructive or state-changing actions.
From the tool's definition Tool description explicitly states "Read a DocumentReference by id" with content URLs "fetchable via get_binary". The verb 'Read' combined with retrieval of a specific resource by identifier indicates pure data retrieval with no side effects.
Attacks that exploit this kind of access
Read a DocumentReference by id (content URLs fetchable via get_binary). It is categorised as a Read tool in the Healow MCP Server, which means it retrieves data without modifying state.
Register the Healow MCP server in PolicyLayer and add a rule for get_document_reference: 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 Healow. Nothing to install.
get_document_reference is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_document_reference 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 get_document_reference. 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.
get_document_reference is provided by the Healow MCP server (voysi-ia/healow-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →