Retrieve laboratory observations for a specific patient.
AI agents call get_patient_lab_results to retrieve information from FHIR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves healthcare data (lab results) without creating, modifying, deleting, or executing operations. It is a read-only query operation. Severity is medium (not low) because unauthorized access to laboratory results could expose sensitive personal health information (PHI) under regulations like HIPAA, making misuse harmful even though the operation itself is non-destructive.
From the tool's definition Tool name 'get_patient_lab_results' and description 'Retrieve laboratory observations for a specific patient' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Retrieve laboratory observations for a specific patient. It is categorised as a Read tool in the FHIR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FHIR MCP Server MCP server in PolicyLayer and add a rule for get_patient_lab_results: 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 FHIR MCP Server. Nothing to install.
get_patient_lab_results 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_patient_lab_results 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_patient_lab_results. 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_patient_lab_results is provided by the FHIR MCP Server MCP server (sdesani/mcp-fhir). 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 →