openehr_composition_delete
A destructive tool on the openEHR MCP server.
This record as markdown: /tools/deak-ai-openehr-mcp-server/openehr-composition-delete.md
What openehr_composition_delete does on openEHR MCP Server
AI agents call openehr_composition_delete to permanently remove resources in openEHR MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why openehr_composition_delete is rated Critical
The 'delete' verb combined with the openEHR context (healthcare data management system) indicates permanent removal of clinical compositions. This cannot be undone and affects patient medical records. Although description is empty, the tool name alone provides sufficient evidence for Destructive classification.
From the tool's definition Tool name is 'openehr_composition_delete' with 'delete' action on composition data in an EHR system. Context shows sibling tools perform create, get, update, list operations, and this tool's name unambiguously indicates irreversible deletion of a composition…
Attacks that exploit this kind of access
The rule that runs openehr_composition_delete 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_delete, this is the rule to start with:
openehr_composition_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect openEHR MCP Server, apply this rule, and every openehr_composition_delete call is checked against it from then on.
Questions about openehr_composition_delete
openehr_composition_delete is a destructive tool on the openEHR MCP Server MCP server. It is categorised as a Destructive tool in the openEHR MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the openEHR MCP Server MCP server in PolicyLayer and add a rule for openehr_composition_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 openEHR MCP Server. Nothing to install.
openehr_composition_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 openehr_composition_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 openehr_composition_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.
openehr_composition_delete 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.
Across the catalogue