Check doctor availability for appointment booking. Behavior: - If preferred_date AND preferred_slot_time are provided: checks if that specific slot is available and returns a direct response (non-elicitation). - If date/time are NOT provided: returns elicitation response with available option...
Part of the Eka EMR MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke doctor_availability_elicitation to trigger processes or run actions in Eka EMR. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
doctor_availability_elicitation can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
doctor_availability_elicitation:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Eka EMR policy for all 17 tools.
Agents calling execute-class tools like doctor_availability_elicitation have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
doctor_availability_elicitation is one of the high-risk operations in Eka EMR. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Check doctor availability for appointment booking. Behavior: - If preferred_date AND preferred_slot_time are provided: checks if that specific slot is available and returns a direct response (non-elicitation). - If date/time are NOT provided: returns elicitation response with available options for the user to choose from. Flow: 1. Fetch doctor details 2. Validate/resolve hospital (if provided & matches, use it; else return all doctor's hospitals) 3. Fetch available dates (check if preferred_date is available) 4. Fetch available slots (check if preferred_slot_time is available) Trigger Keywords: check availability, doctor available, when can I book, appointment slots, available times for doctor Returns: - If date+time provided: Direct availability check result - If date+time missing: UI component format (doctor_card) with availability and callbacks for elicitation. It is categorised as a Execute tool in the Eka EMR MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for doctor_availability_elicitation. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Eka EMR MCP server.
doctor_availability_elicitation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the doctor_availability_elicitation 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 doctor_availability_elicitation. 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.
doctor_availability_elicitation 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