Retrieve basic profile information for a clinic without doctor or appointment context. When to Use This Tool Use this tool when only clinic-level details such as address or facilities are required. For full clinic context including doctors and appointments, use get_comprehensive_clinic_profile. ...
Part of the Eka EMR MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_clinic_details_basic 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_clinic_details_basic 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.
tools:
get_clinic_details_basic:
rules:
- action: allowSee the full Eka EMR policy for all 17 tools.
Agents calling read-class tools like get_clinic_details_basic have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieve basic profile information for a clinic without doctor or appointment context. When to Use This Tool Use this tool when only clinic-level details such as address or facilities are required. For full clinic context including doctors and appointments, use get_comprehensive_clinic_profile. Trigger Keywords / Phrases clinic details, clinic information, clinic address, clinic profile What to Return Returns basic clinic profile data without doctor associations or appointment history.. It is categorised as a Read tool in the Eka EMR MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_clinic_details_basic. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Eka EMR MCP server.
get_clinic_details_basic 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_clinic_details_basic rule in your Intercept 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 Intercept policy for get_clinic_details_basic. 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_clinic_details_basic is provided by the Eka EMR MCP server (eka-care/emr). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept