AI agents call openemr_questionnaire_trends 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 existing patient questionnaire data (PHQ-9 depression scores over time) without modifying, creating, or deleting any records. It is a pure read operation that presents clinical information for review. While the data is sensitive (healthcare records), the tool itself performs no side effects or state changes.
From the tool's definition Tool name contains 'trends' and description states 'Return longitudinal questionnaire score trajectories' — a retrieval operation with no modification, deletion, or execution capabilities. Returns historical PHQ-9 depression screening data.
Attacks that exploit this kind of access
Return longitudinal questionnaire score trajectories for a patient (PHQ-9 depression screening). 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_questionnaire_trends: 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_questionnaire_trends 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_questionnaire_trends 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_questionnaire_trends. 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_questionnaire_trends 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 →