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 fo...
Part of the Eka EMR server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"doctor_availability_elicitation": {
"limits": [
{
"counter": "doctor_availability_elicitation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Eka EMR policy for all 17 tools.
These attack patterns abuse exactly the kind of access doctor_availability_elicitation gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Eka EMR MCP server in PolicyLayer and add a rule for doctor_availability_elicitation: 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.
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 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 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). 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.