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

openehr_ehr_get_by_subject

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-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.

Questions about openehr_ehr_get_by_subject

What does the openehr_ehr_get_by_subject tool do? +

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.

How do I enforce a policy on openehr_ehr_get_by_subject? +

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.

What risk level is openehr_ehr_get_by_subject? +

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

Can I rate-limit openehr_ehr_get_by_subject? +

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.

How do I block openehr_ehr_get_by_subject completely? +

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.

What MCP server provides openehr_ehr_get_by_subject? +

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.

// 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.