finance_register_payment

Register a manual payment against an existing charge (cobro). Updates cobro status automatically. Requires confirm: true.

SERVERServicialo SOURCE@servicialo/mcp-server

Critical RISK CLASS

Category Financial

Parameters 95 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/finance-register-payment.md

WHAT IT DOES

What finance_register_payment does on Servicialo

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

Parameter	Type	Required
`tipo`	string	Yes
`fecha`	string	—
`monto`	number	Yes
`apiKey`	string	—
`cobroId`	string	Yes
`confirm`	boolean	Yes
`orgSlug`	string	Yes
`descripcion`	string	—
`idempotencyKey`	string	—

Parameters from the server's own tool schema.

RISK

Why finance_register_payment is rated Critical

This tool explicitly records a payment against an existing financial charge, directly committing a financial transaction. The 'confirm: true' requirement signals irreversibility. Misuse could result in fraudulent or erroneous payment records, making this a critical financial risk.

From the tool's definition 'Register a manual payment against an existing charge (cobro). Updates cobro status automatically. Requires confirm: true.'

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs finance_register_payment safely

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

finance_register_payment Approval-gated

Any call to finance_register_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": {
    "finance_register_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 Servicialo, apply this rule, and every finance_register_payment call is checked against it from then on.

FAQ

Questions about finance_register_payment

What does the finance_register_payment tool do? +

Register a manual payment against an existing charge (cobro). Updates cobro status automatically. Requires confirm: true. It is categorised as a Financial tool in the Servicialo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does finance_register_payment accept? +

finance_register_payment accepts 9 parameters: tipo, fecha, monto, apiKey, cobroId, confirm, orgSlug, descripcion, idempotencyKey. Required: tipo, monto, cobroId, confirm, orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on finance_register_payment? +

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

What risk level is finance_register_payment? +

finance_register_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 finance_register_payment? +

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

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

finance_register_payment is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →create_payment on Shopmonkey MCP Server →invoice_issued_cash_payment on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

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