Archives a patient profile. Recommended Usage: Use to mark a patient profile as archived Do not use for permanently deleting patient data or creating/updating profiles. Trigger Keywords: archive patient, delete patient, toggle patient archive status, remove for now Returns: Success message confir...
Part of the Eka EMR server.
Free to start. No card required.
AI agents may call archive_patient to permanently remove or destroy resources in Eka EMR. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call archive_patient in a loop, permanently destroying resources in Eka EMR. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"archive_patient"
]
}See the full Eka EMR policy for all 17 tools.
These attack patterns abuse exactly the kind of access archive_patient gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Archives a patient profile. Recommended Usage: Use to mark a patient profile as archived Do not use for permanently deleting patient data or creating/updating profiles. Trigger Keywords: archive patient, delete patient, toggle patient archive status, remove for now Returns: Success message confirming profile removal. It is categorised as a Destructive tool in the Eka EMR MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eka EMR MCP server in PolicyLayer and add a rule for archive_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.
archive_patient is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archive_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 archive_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.
archive_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.