get_patient_appointments
AI agents call get_patient_appointments 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.
The 'get_' prefix and pattern of sibling tools (get_allergy_by_id, get_condition_by_id, get_observation_by_id, etc.) establish this as a retrieval operation with no side effects. While the description is empty, the naming convention and server context—healthcare FHIR APIs for patient data—clearly indicate a query/read operation.
From the tool's definition Tool name indicates retrieval of patient appointments via FHIR API; sibling tools are all 'get_*' operations that retrieve specific healthcare data without modification; Oracle Millennium Platform context indicates read access to patient records.
Attacks that exploit this kind of access
get_patient_appointments. 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_appointments: 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_appointments 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_appointments 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_appointments. 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_appointments 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 →