Search for medication requests/prescriptions (e.g., diabetes medications)
AI agents call search_medication_requests 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 medication request/prescription data from a FHIR system without creating, modifying, or deleting records. It is a read operation. However, severity is elevated to 'high' because medication request data is highly sensitive PHI (Protected Health Information) containing details about prescribed medications, dosages, and patient treatments.
From the tool's definition Tool description states 'Search for medication requests/prescriptions' - a retrieval operation with no side effects. The name and description indicate data querying only, consistent with FHIR search operations.
Attacks that exploit this kind of access
Search for medication requests/prescriptions (e.g., diabetes medications). 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_medication_requests: 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_medication_requests 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_medication_requests 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_medication_requests. 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_medication_requests is provided by the FHIR MCP Server MCP server (jcafazzo/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 →