AI agents call openemr_health_trajectory 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 performs data retrieval and analysis (aggregation of labs, vitals, questionnaires) and generates computed alerts based on existing records. These are read-only operations that query and analyze patient health metrics without creating, modifying, deleting, or executing code.
From the tool's definition Tool description states it 'aggregates' and 'computes' clinical data trajectories and drift alerts—operations that retrieve and analyze existing patient data without modifying, deleting, or executing external operations. No side effects mentioned.
Attacks that exploit this kind of access
Aggregate all metric trajectories (labs, vitals, questionnaires) and compute clinical drift alerts 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_health_trajectory: 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_health_trajectory 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_health_trajectory 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_health_trajectory. 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_health_trajectory 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 →