RECOMMENDED: Get comprehensive patient profile including detailed appointment history with enriched doctor and clinic information. This is the preferred tool for getting patient information as it provides complete context including appointment history with doctor names, clinic details, and appoin...
Part of the Eka EMR server.
Free to start. No card required.
AI agents call get_comprehensive_patient_profile to retrieve information from Eka EMR without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_comprehensive_patient_profile only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_comprehensive_patient_profile": {}
}
}See the full Eka EMR policy for all 17 tools.
These attack patterns abuse exactly the kind of access get_comprehensive_patient_profile gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
RECOMMENDED: Get comprehensive patient profile including detailed appointment history with enriched doctor and clinic information. This is the preferred tool for getting patient information as it provides complete context including appointment history with doctor names, clinic details, and appointment status. Use this instead of get_patient_details_basic unless you specifically need only profile data. Use when: - "Show patient details" - "Patient medical history" - Need appointments with doctor/clinic names Returns: Complete patient profile with enriched appointment history including doctor and clinic details. It is categorised as a Read tool in the Eka EMR MCP Server, which means it retrieves data without modifying state.
Register the Eka EMR MCP server in PolicyLayer and add a rule for get_comprehensive_patient_profile: 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 Eka EMR. Nothing to install.
get_comprehensive_patient_profile 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 get_comprehensive_patient_profile 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 get_comprehensive_patient_profile. 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.
get_comprehensive_patient_profile is provided by the Eka EMR MCP server (eka-care/emr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Eka EMR tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.