charge_invoice_external

Charge an invoice via offline payment (cash/check/wire). POST /invoices/{invoiceId}/charge with paymentType: offlinePaymentProvider. AMOUNT IN CENTS: e.g. 5500 = $55.00. Required: invoiceId, amount (integer cents).

Server Rebillia MCP Server rhinosaas/rebillia-mcp-server
Category Financial
Risk class Critical
Parameters 00 required

What charge_invoice_external does on Rebillia MCP Server

AI agents use charge_invoice_external to commit financial operations through Rebillia MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why charge_invoice_external needs a policy

This tool moves money by charging customers for invoices through offline payment methods. It commits financial obligations and represents a critical financial operation. Even though it processes offline payments, it records and executes charges in a billing system, making it categorically Financial.

From the tool's definition Tool charges an invoice by processing an offline payment (cash/check/wire). Description explicitly states 'Charge an invoice' and specifies amount in cents, confirming monetary transaction processing.

Questions about charge_invoice_external

What does the charge_invoice_external tool do? +

Charge an invoice via offline payment (cash/check/wire). POST /invoices/{invoiceId}/charge with paymentType: offlinePaymentProvider. AMOUNT IN CENTS: e.g. 5500 = $55.00. Required: invoiceId, amount (integer cents). It is categorised as a Financial tool in the Rebillia MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on charge_invoice_external? +

Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for charge_invoice_external: 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 Rebillia MCP Server. Nothing to install.

What risk level is charge_invoice_external? +

charge_invoice_external is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit charge_invoice_external? +

Yes. Add a rate_limit block to the charge_invoice_external 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.

How do I block charge_invoice_external completely? +

Set action: deny in the PolicyLayer policy for charge_invoice_external. 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.

What MCP server provides charge_invoice_external? +

charge_invoice_external is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.