openehr_ehr_list

A read tool on the openEHR MCP server.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deak-ai-openehr-mcp-server/openehr-ehr-list.md

WHAT IT DOES

What openehr_ehr_list does on openEHR MCP Server

AI agents call openehr_ehr_list 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.

RISK

Why openehr_ehr_list is rated Low

A list operation retrieves or queries data without side effects. Although the tool description is empty, the naming convention and context from sibling tools strongly indicate this performs a read-only query to enumerate Electronic Health Records. No data is modified, deleted, or executed.

From the tool's definition Tool name 'openehr_ehr_list' and server description indicate listing EHRs. The sibling tools include 'openehr_ehr_create', 'openehr_ehr_get', and 'openehr_composition_list', suggesting this follows a standard CRUD pattern where 'list' operations are read-only…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

openehr_ehr_list Allowed

openehr_ehr_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY 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_ehr_list call is checked against it from then on.

FAQ

Questions about openehr_ehr_list

What does the openehr_ehr_list tool do? +

openehr_ehr_list is a read tool on the openEHR MCP Server MCP server. It is categorised as a Read tool in the openEHR MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openehr_ehr_list? +

Register the openEHR MCP Server MCP server in PolicyLayer and add a rule for openehr_ehr_list: 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_ehr_list? +

openehr_ehr_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit openehr_ehr_list? +

Yes. Add a rate_limit block to the openehr_ehr_list 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_ehr_list completely? +

Set action: deny in the PolicyLayer policy for openehr_ehr_list. 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_ehr_list? +

openehr_ehr_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →