This record as markdown: /tools/aiwerk-mcp-server-ghl/invoices-update-invoice.md
What invoices_update_invoice does on Ghl
AI agents use invoices_update_invoice to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name to be updated |
altId | string | — | location Id / company Id based on altType Defaults to GHL_LOCATION_ID when omitted. |
title | string | — | Title for the invoice |
altType | string | — | Alt Type Defaults to GHL_LOCATION_ID when omitted. |
dueDate | string | Yes | Due date in YYYY-MM-DD format |
currency | string | Yes | Currency |
discount | object | — | |
liveMode | boolean | — | Payment mode |
contactId | string | — | Id of the contact which you need to send the invoice |
invoiceId | string | Yes | Invoice Id |
issueDate | string | Yes | Issue date in YYYY-MM-DD format |
termsNotes | string | — | Terms notes, Also supports HTML markups |
Parameters from the server's own tool schema.
Why invoices_update_invoice is rated Medium
An AI agent can call invoices_update_invoice faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (50 properties)
Attacks that exploit this kind of access
The rule that runs invoices_update_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invoices_update_invoice, this is the rule to start with:
invoices_update_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 Ghl, apply this rule, and every invoices_update_invoice call is checked against it from then on.
Questions about invoices_update_invoice
Update invoice. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
invoices_update_invoice accepts 12 parameters: name, altId, title, altType, dueDate, currency, discount, liveMode, contactId, invoiceId, issueDate, termsNotes. Required: name, dueDate, currency, invoiceId, issueDate. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for invoices_update_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 Ghl. Nothing to install.
invoices_update_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 invoices_update_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 invoices_update_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.
invoices_update_invoice is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue