finance_send_confirmations
Send pending confirmation digest to clients. Groups all pending_confirmation charges by client and sends a single message per client via WhatsApp or email. Creates confirmation tokens and sets a grace period for auto-confirmation. Requires confirm: true.
This record as markdown: /tools/com-servicialo-mcp-server/finance-send-confirmations.md
What finance_send_confirmations does on Servicialo
AI agents use finance_send_confirmations 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 | Description |
|---|---|---|---|
apiKey | string | — | |
channel | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
clientId | string | — |
Parameters from the server's own tool schema.
Why finance_send_confirmations is rated Critical
This tool initiates financial confirmation flows for charges owed by clients, creates binding confirmation tokens, and sets auto-confirmation grace periods — meaning charges can be automatically committed without further intervention. Misuse could result in unauthorized financial obligations being sent to and confirmed by clients, making this a Financial category tool with critical severity.
From the tool's definition 'pending_confirmation charges', 'confirmation tokens', 'auto-confirmation', 'finance_send_confirmations'
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs finance_send_confirmations 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_send_confirmations, this is the rule to start with:
Any call to finance_send_confirmations is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every finance_send_confirmations call is checked against it from then on.
Questions about finance_send_confirmations
Send pending confirmation digest to clients. Groups all pending_confirmation charges by client and sends a single message per client via WhatsApp or email. Creates confirmation tokens and sets a grace period for auto-confirmation. 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.
finance_send_confirmations accepts 5 parameters: apiKey, channel, confirm, orgSlug, clientId. Required: confirm, orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for finance_send_confirmations: 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.
finance_send_confirmations 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 finance_send_confirmations 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 finance_send_confirmations. 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.
finance_send_confirmations 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.
More on Servicialo, and thousands of servers like it.
Across the catalogue