invoices_record_invoice
Record a manual payment for an invoice
This record as markdown: /tools/aiwerk-mcp-server-ghl/invoices-record-invoice.md
What invoices_record_invoice does on Ghl
AI agents call invoices_record_invoice to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
card | object | Yes | |
meta | object | — | |
mode | string | Yes | manual payment method |
altId | string | — | location Id / company Id based on altType Defaults to GHL_LOCATION_ID when omitted. |
notes | string | Yes | Any note to be recorded with the transaction |
amount | number | — | Amount to be paid against the invoice. |
cheque | object | Yes | |
altType | string | — | Alt Type Defaults to GHL_LOCATION_ID when omitted. |
invoiceId | string | Yes | Invoice Id |
fulfilledAt | string | — | Updated At to be recorded against the invoice. |
paymentScheduleIds | array | — | Payment Schedule Ids to be recorded against the invoice. |
Parameters from the server's own tool schema.
Why invoices_record_invoice is rated Low
Even though invoices_record_invoice only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs invoices_record_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_record_invoice, this is the rule to start with:
invoices_record_invoice is read-only, so it stays allowed. 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_record_invoice call is checked against it from then on.
Questions about invoices_record_invoice
Record a manual payment for an invoice. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
invoices_record_invoice accepts 11 parameters: card, meta, mode, altId, notes, amount, cheque, altType, invoiceId, fulfilledAt, paymentScheduleIds. Required: card, mode, notes, cheque, 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_record_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_record_invoice is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the invoices_record_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_record_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_record_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