openehr_template_example_composition

What openehr_template_example_composition does on openEHR MCP Server

AI agents call openehr_template_example_composition to retrieve information from openEHR MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why openehr_template_example_composition is rated Low

Based on naming convention, this tool likely retrieves or displays template examples for compositions—a read-only operation with no side effects. The absence of action verbs like 'create', 'delete', 'update', 'execute' in the name indicates passive data retrieval. The context of sibling tools (which include explicit CRUD operations) suggests this is a lookup/reference tool.

From the tool's definition Tool name 'openehr_template_example_composition' suggests retrieval of example/template data. The suffix pattern '_example_' and '_composition' aligns with query/fetch operations. No description provided, reducing confidence slightly.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "openehr_template_example_composition": {}
  }
}

Questions about openehr_template_example_composition