This record as markdown: /tools/ghl/send-invoice.md
What send_invoice does on Ghl
AI agents use 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 |
emailTo | string | — | Email address to send to |
message | string | — | Email message |
subject | string | — | Email subject |
invoiceId | string | Yes | Invoice ID |
Parameters from the server's own tool schema.
Why send_invoice is rated Critical
Sending an invoice commits a financial obligation by creating a legally recognized demand for payment. This is a financial operation that can result in money movement and alters the customer's accounting records. While the tool itself does not directly transfer funds, it initiates the financial chain that leads to payment obligations.
From the tool's definition Tool name is 'send_invoice' with description 'Send an invoice to customer'. An invoice is a financial document that creates a payment obligation and initiates a financial transaction.
Attacks that exploit this kind of access
The rule that runs 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 send_invoice, this is the rule to start with:
Any call to 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 send_invoice call is checked against it from then on.
Questions about send_invoice
Send an invoice to customer. 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.
send_invoice accepts 5 parameters: altId, emailTo, message, subject, invoiceId. Required: 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 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.
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 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 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.
send_invoice is provided by the Ghl MCP server (ghl-mcp-server). 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