search_appointments_by_date
AI agents call search_appointments_by_date 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 tool appears designed to retrieve appointment records filtered by date—a read operation with no modification or destructive capability. However, severity is elevated to 'medium' rather than 'low' because healthcare appointment data is sensitive PII that could expose patient scheduling patterns, availability, and clinical care information.
From the tool's definition Tool name contains 'search' and 'by_date', indicating data retrieval. Sibling tools follow a consistent 'get_*' pattern for reading FHIR data. Description is empty but naming convention strongly suggests read-only query operation.
Attacks that exploit this kind of access
search_appointments_by_date. 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 search_appointments_by_date: 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.
search_appointments_by_date 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 search_appointments_by_date 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 search_appointments_by_date. 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.
search_appointments_by_date 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 →