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 appointmen...
Part of the Eka EMR MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
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. Intercept'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.
tools:
complete_appointment:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Eka EMR policy for all 17 tools.
Agents calling write-class tools like complete_appointment have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
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.
Add a rule in your Intercept YAML policy under the tools section for complete_appointment. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Eka EMR MCP server.
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 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 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). 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