This record as markdown: /tools/aiwerk-mcp-server-ghl/invoices-send-invoice.md
What invoices_send_invoice does on Ghl
AI agents use invoices_send_invoice to commit financial operations through Ghl, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
altId | string | — | location Id / company Id based on altType Defaults to GHL_LOCATION_ID when omitted. |
action | string | Yes | |
userId | string | Yes | Please ensure that the UserId corresponds to an authorized personnel, either by an employee ID or agency ID, to access this location. This account will serve as |
altType | string | — | Alt Type Defaults to GHL_LOCATION_ID when omitted. |
liveMode | boolean | Yes | |
sentFrom | object | — | sender details for invoice, valid only if invoice is not sent manually |
invoiceId | string | Yes | Invoice Id |
autoPayment | object | — | auto-payment configuration |
Parameters from the server's own tool schema.
Why invoices_send_invoice is rated Critical
invoices_send_invoice moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Risk signalsHigh parameter count (21 properties)
Attacks that exploit this kind of access
The rule that runs invoices_send_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_send_invoice, this is the rule to start with:
Any call to invoices_send_invoice is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every invoices_send_invoice call is checked against it from then on.
Questions about invoices_send_invoice
Send invoice. It is categorised as a Financial tool in the Ghl MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
invoices_send_invoice accepts 8 parameters: altId, action, userId, altType, liveMode, sentFrom, invoiceId, autoPayment. Required: action, userId, liveMode, invoiceId. 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_send_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_send_invoice is a Financial 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 invoices_send_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_send_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_send_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.
Across the catalogue