openehr_ehr_get_by_subject
A read tool on the openEHR MCP server.
This record as markdown: /tools/deak-ai-openehr-mcp-server/openehr-ehr-get-by-subject.md
What openehr_ehr_get_by_subject does on openEHR MCP Server
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.
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 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.
Attacks that exploit this kind of access
The rule that runs openehr_ehr_get_by_subject 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_get_by_subject, this is the rule to start with:
openehr_ehr_get_by_subject is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect openEHR MCP Server, apply this rule, and every openehr_ehr_get_by_subject call is checked against it from then on.
Questions about openehr_ehr_get_by_subject
openehr_ehr_get_by_subject 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.
Register the openEHR MCP Server MCP server in PolicyLayer and add a rule for openehr_ehr_get_by_subject: 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_ehr_get_by_subject is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the openehr_ehr_get_by_subject 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_ehr_get_by_subject. 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_ehr_get_by_subject 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.
This server
Across the catalogue