Retrieve a list of appointments with basic data containing entity IDs only, without patient, doctor, or clinic details. When to Use This Tool Use this tool only when raw appointment records are required. Use show_appointments_enriched otherwise. This tool is intended for internal workflows, debug...
Part of the Eka EMR server.
Free to start. No card required.
AI agents call show_appointments_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 show_appointments_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.
{
"version": "1",
"default": "deny",
"tools": {
"show_appointments_basic": {}
}
}See the full Eka EMR policy for all 17 tools.
These attack patterns abuse exactly the kind of access show_appointments_basic 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.
Retrieve a list of appointments with basic data containing entity IDs only, without patient, doctor, or clinic details. When to Use This Tool Use this tool only when raw appointment records are required. Use show_appointments_enriched otherwise. This tool is intended for internal workflows, debugging, or follow-up calls where entity details will be resolved separately. Trigger Keywords / Phrases raw appointments, appointment ids, basic appointment list, internal lookup, debug appointments, lightweight appointment data Returns: Basic appointments with entity IDs only If no appointments match the filters, returns an empty appointments array. Timestamps are Unix epoch (UTC-based). IMPORTANT: Always use Python/bash to convert timestamps - never do mental math. Use the below code. python3 -c "import datetime; print(datetime.datetime.fromtimestamp(TIMESTAMP, tz=datetime.timezone(datetime.timedelta(hours=5, minutes=30))).strftime('%I:%M %p IST'))". 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 show_appointments_basic: 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.
show_appointments_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 show_appointments_basic 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 show_appointments_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.
show_appointments_basic 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.