create_invoice
Create a new invoice for a customer. Optionally include line items inline. Returns the new invoiceId.
This record as markdown: /tools/io-favcrm-favcrm/create-invoice.md
What create_invoice does on FavCRM
AI agents use create_invoice to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Free-form notes shown on the invoice |
dueDate | string | — | Due date (ISO 8601 date) |
currency | string | — | ISO currency code (defaults to company default) |
accountId | string | Yes | Customer accountId (CRM account) |
lineItems | array | — | Line items to bill — totals are computed server-side |
Parameters from the server's own tool schema.
Why create_invoice is rated Medium
This tool creates a new invoice record, which is a reversible write operation (invoices can typically be voided or deleted). However, invoices represent financial obligations and commitments to customers, giving it a high severity blast radius if misused — e.g., generating fraudulent or erroneous invoices.
From the tool's definition Create a new invoice for a customer. Optionally include line items inline. Returns the new invoiceId.
Attacks that exploit this kind of access
The rule that runs create_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_invoice, this is the rule to start with:
create_invoice stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every create_invoice call is checked against it from then on.
Questions about create_invoice
Create a new invoice for a customer. Optionally include line items inline. Returns the new invoiceId. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_invoice accepts 5 parameters: notes, dueDate, currency, accountId, lineItems. Required: accountId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue