delete_invoice
AI agents call delete_invoice 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.
This tool permanently removes invoice data from the practice management system. Invoice deletion is irreversible and affects critical financial records used for accounting, auditing, and business operations. While the description is empty, the tool name unambiguously indicates a destructive operation on financial documents.
From the tool's definition Tool name 'delete_invoice' explicitly indicates irreversible deletion of financial records. The sibling tools include 'create_invoice' (Write), and the server manages 'practice management system' data including financial documents.
Attacks that exploit this kind of access
delete_invoice. 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.
Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for delete_invoice: 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.
delete_invoice 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 delete_invoice 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 delete_invoice. 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.
delete_invoice 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.
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 →