record_invoice_payment

Record a manual payment against an invoice (cash, bank transfer, cheque, card terminal). Updates invoice status to PARTIAL or PAID based on the running total.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Critical RISK CLASS

Category Financial

Parameters 53 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/record-invoice-payment.md

WHAT IT DOES

What record_invoice_payment does on FavCRM

AI agents use record_invoice_payment to commit financial operations through FavCRM, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`note`	string	—	Internal note about this payment
`amount`	string	Yes	Payment amount as decimal string, e.g. "100.00"
`method`	string	Yes	Payment method
`invoiceId`	string	Yes	Invoice ID to record payment against
`reference`	string	—	External reference (cheque number, bank transfer ID)

Parameters from the server's own tool schema.

RISK

Why record_invoice_payment is rated Critical

This tool directly records financial transactions (payments) against invoices and modifies their payment status. It commits financial obligations and records monetary flows, making it a Financial category tool. Misuse could result in fraudulent payment records, incorrect financial statements, or unauthorized marking of invoices as paid — hence critical severity.

From the tool's definition Record a manual payment against an invoice (cash, bank transfer, cheque, card terminal). Updates invoice status to PARTIAL or PAID based on the running total.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_invoice_payment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_invoice_payment, this is the rule to start with:

record_invoice_payment Approval-gated

Any call to record_invoice_payment is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_invoice_payment": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every record_invoice_payment call is checked against it from then on.

FAQ

Questions about record_invoice_payment

What does the record_invoice_payment tool do? +

Record a manual payment against an invoice (cash, bank transfer, cheque, card terminal). Updates invoice status to PARTIAL or PAID based on the running total. It is categorised as a Financial tool in the FavCRM MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does record_invoice_payment accept? +

record_invoice_payment accepts 5 parameters: note, amount, method, invoiceId, reference. Required: amount, method, invoiceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on record_invoice_payment? +

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

What risk level is record_invoice_payment? +

record_invoice_payment 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 record_invoice_payment? +

Yes. Add a rate_limit block to the record_invoice_payment 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 record_invoice_payment completely? +

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

record_invoice_payment is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →create_payment on Shopmonkey MCP Server →pay_invoice on Bitcoin MCP Server →create_contract_payment on AdButler → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →