AI agents call openemr_appointment_list to retrieve information from Openemr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves appointment data for a patient without creating, modifying, deleting, or executing any operations. It is a simple read operation on existing healthcare records, which falls squarely into the Read category. The severity is low because appointment data leakage, while a privacy concern, does not enable direct harm compared to medication lists or clinical interventions.
From the tool's definition Tool name 'openemr_appointment_list' and description 'List upcoming appointments for a patient' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List upcoming appointments for a patient. It is categorised as a Read tool in the Openemr MCP Server, which means it retrieves data without modifying state.
Register the Openemr MCP server in PolicyLayer and add a rule for openemr_appointment_list: 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 Openemr. Nothing to install.
openemr_appointment_list 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 openemr_appointment_list 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 openemr_appointment_list. 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.
openemr_appointment_list is provided by the Openemr MCP server (shruti-jn/openemr-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 →