AI agents call openemr_symptom_lookup 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 retrieves diagnostic reference information based on input symptoms and returns results (conditions with urgency levels). It is a passive lookup/search operation analogous to querying a medical database or reference guide. No patient data is modified, no commands are executed, and no irreversible changes occur.
From the tool's definition Tool 'openemr_symptom_lookup' describes a lookup operation that 'returns ranked conditions' — a retrieval and query of medical reference data with no modification, creation, or execution of side effects.
Attacks that exploit this kind of access
Look up possible conditions for a list of symptoms. Returns ranked conditions with urgency level and medical disclaimer. 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_symptom_lookup: 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_symptom_lookup 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_symptom_lookup 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_symptom_lookup. 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_symptom_lookup 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 →