Get patient observations by specific FHIR category (vital-signs, laboratory, imaging, exam, procedure, survey, social-history, therapy, activity)
AI agents call get_observations_by_category to retrieve information from FHIR Careplan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation that queries existing FHIR observations without side effects. It returns clinical data for informational purposes only. No data is created, modified, deleted, or executed. The sibling tools (find_patient, get_patient_allergies, get_patient_conditions, etc.) confirm this is part of a read-only clinical data access pattern.
From the tool's definition Tool retrieves patient observations filtered by FHIR category. The description uses 'Get' and lists observation categories (vital-signs, laboratory, imaging, exam, procedure, survey, social-history, therapy, activity) with no mention of modification,…
Attacks that exploit this kind of access
Get patient observations by specific FHIR category (vital-signs, laboratory, imaging, exam, procedure, survey, social-history, therapy, activity). It is categorised as a Read tool in the FHIR Careplan MCP Server, which means it retrieves data without modifying state.
Register the FHIR Careplan MCP server in PolicyLayer and add a rule for get_observations_by_category: 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 Careplan. Nothing to install.
get_observations_by_category 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_observations_by_category 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_observations_by_category. 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_observations_by_category is provided by the FHIR Careplan MCP server (kushagra-dutta/fhir-mcp). 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 →