openehr_ehr_create
A write tool on the openEHR MCP server.
This record as markdown: /tools/deak-ai-openehr-mcp-server/openehr-ehr-create.md
What openehr_ehr_create does on openEHR MCP Server
AI agents use openehr_ehr_create to create or update resources in openEHR MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your openEHR MCP Server environment.
Why openehr_ehr_create is rated Medium
Creating a new EHR is a Write operation—it creates data reversibly. It is not Destructive (no deletion), Execute (no arbitrary code execution), or Financial. Severity is high because EHRs contain sensitive patient health information; unauthorized creation could compromise data integrity and create false medical records.
From the tool's definition Tool name 'openehr_ehr_create' indicates creation of a new EHR (Electronic Health Record). The server description confirms it enables 'creating compositions, managing EHRs'.
Attacks that exploit this kind of access
The rule that runs openehr_ehr_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and openEHR MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openehr_ehr_create, this is the rule to start with:
openehr_ehr_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect openEHR MCP Server, apply this rule, and every openehr_ehr_create call is checked against it from then on.
Questions about openehr_ehr_create
openehr_ehr_create is a write tool on the openEHR MCP Server MCP server. It is categorised as a Write tool in the openEHR MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the openEHR MCP Server MCP server in PolicyLayer and add a rule for openehr_ehr_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 openEHR MCP Server. Nothing to install.
openehr_ehr_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 openehr_ehr_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 openehr_ehr_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.
openehr_ehr_create is provided by the openEHR MCP Server MCP server (deak-ai/openehr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on openEHR MCP Server, and thousands of servers like it.
This server
Across the catalogue