Mark an appointment as completed. When to Use This Tool Use this tool when the appointment has concluded and needs to be marked as completed in the system. This tool should be called only after the appointment has taken place. User intent should be explicit, as this action updates the appointment...
Part of the Eka EMR server.
Free to start. No card required.
AI agents use complete_appointment to create or modify resources in Eka EMR. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call complete_appointment repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Eka EMR.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"complete_appointment": {
"limits": [
{
"counter": "complete_appointment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Eka EMR policy for all 17 tools.
These attack patterns abuse exactly the kind of access complete_appointment gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark an appointment as completed. When to Use This Tool Use this tool when the appointment has concluded and needs to be marked as completed in the system. This tool should be called only after the appointment has taken place. User intent should be explicit, as this action updates the appointment’s final state. Trigger Keywords / Phrases complete appointment, mark as completed, finish appointment, close visit, appointment done, visit completed Returns: Completion confirmation with updated appointment status. If completion fails, returns an error response. This action should not be retried automatically without user confirmation.. It is categorised as a Write tool in the Eka EMR MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eka EMR MCP server in PolicyLayer and add a rule for complete_appointment: 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.
complete_appointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_appointment 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 complete_appointment. 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.
complete_appointment 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.