Delete a drug safety flag by ID.
AI agents call openemr_drug_safety_flag_delete to permanently remove resources in Openemr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes drug safety flags from the medical record system. Drug safety flags are critical safeguards that alert clinicians to medication risks, contraindications, or adverse events for individual patients. Deleting such flags could hide important safety information, potentially leading to harmful medication decisions.
From the tool's definition The tool name explicitly states 'delete' and the description confirms 'Delete a drug safety flag by ID.' Deletion is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete a drug safety flag by ID. It is categorised as a Destructive tool in the Openemr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openemr MCP server in PolicyLayer and add a rule for openemr_drug_safety_flag_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the openemr_drug_safety_flag_delete 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_delete. 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_delete 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 →