Send an invoice to customer
AI agents use send_invoice to commit financial operations through GoHighLevel MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Sending an invoice is a financial action that creates a binding request for payment and establishes a financial obligation. This falls squarely into the Financial category as it commits financial obligations. The severity is critical because an AI agent misusing this tool could send invoices to wrong customers, create duplicate charges, or fraudulently bill users—resulting in direct financial harm.
From the tool's definition Tool name is 'send_invoice' with description 'Send an invoice to customer'. Invoices are financial documents that create payment obligations and commit the recipient to financial transactions.
Attacks that exploit this kind of access
Send an invoice to customer. It is categorised as a Financial tool in the GoHighLevel MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →