create_invoice
AI agents use create_invoice to create or update resources in Cliniko MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cliniko MCP Server environment.
The tool creates invoices in a medical practice management system. While 'create' typically falls under Write (reversible data creation), invoices represent financial obligations and billing records. However, without evidence that this tool commits actual payments or financial transactions (only creates invoice records), it is classified as Write rather than Financial.
From the tool's definition Tool named 'create_invoice' in a practice management system (Cliniko). The name 'create' indicates write operation (creates data reversibly).
Attacks that exploit this kind of access
create_invoice. It is categorised as a Write tool in the Cliniko MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cliniko MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_invoice 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 create_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 create_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.
create_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 →