# openehr_ehr_get_by_subject

A read tool on the openEHR MCP Server MCP server.

Agent View of the PolicyLayer registry record for `openehr_ehr_get_by_subject`. HTML page: https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-ehr-get-by-subject

## Facts

- Tool: `openehr_ehr_get_by_subject`
- Server: openEHR MCP Server (`deak-ai/openehr-mcp-server`) — https://policylayer.com/tools/deak-ai-openehr-mcp-server.md
- Homepage: https://github.com/deak-ai/openehr-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "openehr_ehr_get_by_subject",
    "arguments": {}
  }
}
```

## Why openehr_ehr_get_by_subject is rated Low

The 'get' prefix strongly indicates a read operation that retrieves EHR data without side effects. EHRbase is a data store, and 'get_by_subject' pattern retrieves records without modification. Low severity because unauthorized access to health records is mitigated by typical API authentication/authorization controls on production EHRbase instances.

From the tool's own definition: "Tool name 'openehr_ehr_get_by_subject' follows the pattern of 'get' operations, which are explicitly listed as read-only queries (get, fetch). The naming convention 'ehr_get' indicates data retrieval."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches openEHR MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "openehr_ehr_get_by_subject": {}
  }
}
```

## Other tools on openEHR MCP Server (12)

- `openehr_composition_delete` — Destructive — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-composition-delete.md
- `openehr_query_adhoc` — Execute — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-query-adhoc.md
- `openehr_composition_get` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-composition-get.md
- `openehr_compositions_list` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-compositions-list.md
- `openehr_ehr_get` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-ehr-get.md
- `openehr_ehr_list` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-ehr-list.md
- `openehr_template_example_composition` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-template-example-composition.md
- `openehr_template_get` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-template-get.md
- `openehr_template_list` — Read — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-template-list.md
- `openehr_composition_create` — Write — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-composition-create.md
- `openehr_composition_update` — Write — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-composition-update.md
- `openehr_ehr_create` — Write — https://policylayer.com/tools/deak-ai-openehr-mcp-server/openehr-ehr-create.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deak-ai-openehr-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deak-ai-openehr-mcp-server