AI agents use openemr_drug_safety_flag_create to create or update resources in Openemr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openemr environment.
This tool creates new data (drug safety flags) in a patient's medical record, which is reversible via the sibling tool openemr_drug_safety_flag_delete. It is Write rather than Execute because it only creates structured safety records, not arbitrary code or external operations.
From the tool's definition Tool name contains 'create' and description states 'Create a drug safety flag for a patient' — this creates new safety alert records in a patient's medical file.
Attacks that exploit this kind of access
Create a drug safety flag for a patient (adverse event, recall, warning, contraindication, or custom note). It is categorised as a Write tool in the Openemr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openemr MCP server in PolicyLayer and add a rule for openemr_drug_safety_flag_create: 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_drug_safety_flag_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the openemr_drug_safety_flag_create 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_drug_safety_flag_create. 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_drug_safety_flag_create 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 →