delete_patient

delete_patient

Server Cliniko MCP Server yasboop/new-cliniko-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_patient does on Cliniko MCP Server

AI agents call delete_patient to permanently remove resources in Cliniko MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_patient needs a policy

The 'delete_patient' operation irreversibly removes patient data from a practice management system. This is a destructive action that cannot be undone and has severe implications in a healthcare context—loss of patient records could violate data retention requirements, disrupt care continuity, and cause operational harm.

From the tool's definition Tool named 'delete_patient' with no description provided. The name explicitly indicates permanent deletion of patient records, which is an irreversible operation.

Questions about delete_patient

What does the delete_patient tool do? +

delete_patient. It is categorised as a Destructive tool in the Cliniko MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_patient? +

Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for delete_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 Cliniko MCP Server. Nothing to install.

What risk level is delete_patient? +

delete_patient is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_patient? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_patient completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_patient? +

delete_patient is provided by the Cliniko MCP Server MCP server (yasboop/new-cliniko-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.