Create and optionally send an invoice (unpaid bill) to a contact. Unlike process_transaction, this does NOT charge a card — it creates an unpaid transaction and can email the contact a payment link. The contact pays the invoice through the payment page. Use pay_invoice to mark it paid via the API...
AI agents use create_invoice to create or update resources in Ontraport MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ontraport MCP Server environment.
Creating an invoice is a reversible write operation (invoices can be deleted or cancelled). The tool does not directly move money or charge payment methods — that happens only if the contact pays via the link or via a separate pay_invoice call. However, the act of emailing a payment link to a contact creates strong financial inducement and exposure.
From the tool's definition Tool description states it 'Create[s]' an invoice and 'can email the contact a payment link' — these are reversible write operations.
Attacks that exploit this kind of access
Create and optionally send an invoice (unpaid bill) to a contact. Unlike process_transaction, this does NOT charge a card — it creates an unpaid transaction and can email the contact a payment link. The contact pays the invoice through the payment page. Use pay_invoice to mark it paid via the API with a card on file. It is categorised as a Write tool in the Ontraport MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for create_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 Ontraport MCP Server. Nothing to install.
create_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 create_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 create_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.
create_invoice is provided by the Ontraport MCP Server MCP server (landonray/mcp-server). 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 →