Updates an existing patient profile with new or corrected information. Recommended Usage: Use when modifying patient details such as name, date of birth, gender, mobile, email, or other demographic/medical fields. Do not use for creating new patient profiles or fetching existing patient data. Tri...
Part of the Eka EMR server.
Free to start. No card required.
AI agents use update_patient 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 update_patient 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": {
"update_patient": {
"limits": [
{
"counter": "update_patient_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 update_patient 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.
Updates an existing patient profile with new or corrected information. Recommended Usage: Use when modifying patient details such as name, date of birth, gender, mobile, email, or other demographic/medical fields. Do not use for creating new patient profiles or fetching existing patient data. Trigger Keywords: update patient, edit patient profile, modify patient details, change patient information, correct patient record Returns: Success message confirming profile update. 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 update_patient: 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.
update_patient 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 update_patient 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 update_patient. 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.
update_patient 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.