openehr_composition_update

A write tool on the openEHR MCP server.

SERVERopenEHR MCP Server SOURCEdeak-ai/openehr-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deak-ai-openehr-mcp-server/openehr-composition-update.md

WHAT IT DOES

What openehr_composition_update does on openEHR MCP Server

AI agents use openehr_composition_update 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.

RISK

Why openehr_composition_update is rated Medium

The tool updates compositions in an openEHR system, which are reversible modifications to electronic health record data. This qualifies as Write category rather than Destructive because updates are non-irreversible changes. Severity is medium because misuse could corrupt or alter sensitive patient health records, but the impact is limited to a single composition unless an agent makes systematic updates.

From the tool's definition Tool name is 'openehr_composition_update' which explicitly indicates modification of existing data (update).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openehr_composition_update 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_composition_update, this is the rule to start with:

openehr_composition_update Rate-limited

openehr_composition_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openehr_composition_update": {
      "limits": [
        {
          "counter": "openehr_composition_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect openEHR MCP Server, apply this rule, and every openehr_composition_update call is checked against it from then on.

FAQ

Questions about openehr_composition_update

What does the openehr_composition_update tool do? +

openehr_composition_update 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.

How do I enforce a policy on openehr_composition_update? +

Register the openEHR MCP Server MCP server in PolicyLayer and add a rule for openehr_composition_update: 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.

What risk level is openehr_composition_update? +

openehr_composition_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit openehr_composition_update? +

Yes. Add a rate_limit block to the openehr_composition_update 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.

How do I block openehr_composition_update completely? +

Set action: deny in the PolicyLayer policy for openehr_composition_update. 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.

What MCP server provides openehr_composition_update? +

openehr_composition_update 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.

KEEP EXPLORING

More on openEHR MCP Server, and thousands of servers like it.

This server

All 13 openEHR MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →