get_patient_immunizations
AI agents call get_patient_immunizations 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 immunization records for a patient—a read-only query with no data modification, deletion, or execution capabilities. It belongs in the Read category. Severity is high (not low/medium) because immunization records are sensitive healthcare data that could enable privacy violations or misuse if exposed to unauthorized agents, but the tool itself has no destructive capability.
From the tool's definition Tool name 'get_patient_immunizations' indicates a retrieval operation on healthcare data. No description provided, but consistent with sibling tools (get_allergy_by_id, get_appointment_by_id, get_condition_by_id, etc.) which are all read-only queries.
Attacks that exploit this kind of access
get_patient_immunizations. 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_immunizations: 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_immunizations 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_immunizations 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_immunizations. 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_immunizations 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 →