Search for patients by email address.
AI agents call search_patients_by_email 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 patient records based on an email query parameter—a read-only operation with no capability to modify, delete, or execute code. However, severity is elevated to 'medium' rather than 'low' because healthcare data is sensitive personal information (PII) and PHI under HIPAA, and unrestricted access via email search could enable unauthorized disclosure of patient records if AI agents lack proper…
From the tool's definition Tool name 'search_patients_by_email' and description 'Search for patients by email address' indicate a retrieval operation with no side effects. The verb 'search' and 'by email' confirm data querying functionality.
Attacks that exploit this kind of access
Search for patients by email address. 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_patients_by_email: 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_patients_by_email 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_patients_by_email 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_patients_by_email. 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_patients_by_email 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 →