New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

openehr_composition_delete

A destructive tool on the openEHR MCP server.

SERVERopenEHR MCP Server SOURCEdeak-ai/openehr-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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…

Questions about openehr_composition_delete

What does the openehr_composition_delete tool do? +

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.

How do I enforce a policy on openehr_composition_delete? +

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.

What risk level is openehr_composition_delete? +

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.

Can I rate-limit openehr_composition_delete? +

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.

How do I block openehr_composition_delete completely? +

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.

What MCP server provides openehr_composition_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of openEHR MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.