get_patient_procedures
AI agents call get_patient_procedures 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 procedure records for a patient from a FHIR API with no side effects—a pure read operation. However, severity is high (not medium) because patient medical procedures are sensitive protected health information (PHI) under HIPAA; unauthorized disclosure poses significant harm to privacy and could enable medical identity theft or discrimination.
From the tool's definition Tool name 'get_patient_procedures' and sibling tools (get_allergy_by_id, get_appointment_by_id, get_condition_by_id, etc.) all follow a 'get_*_by_id' pattern that retrieves FHIR healthcare records without modification.
Attacks that exploit this kind of access
get_patient_procedures. 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_procedures: 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_procedures 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_procedures 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_procedures. 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_procedures 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 →