finance_list_confirmations
List pending charge confirmations and their status. Shows cobros in pending_confirmation state that await client verification. Filter by client or confirmation status (pending, confirmed, disputed, auto_confirmed).
This record as markdown: /tools/com-servicialo-mcp-server/finance-list-confirmations.md
What finance_list_confirmations does on Servicialo
AI agents call finance_list_confirmations to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
status | string | — | |
orgSlug | string | Yes | |
clientId | string | — |
Parameters from the server's own tool schema.
Why finance_list_confirmations is rated Low
This tool retrieves and displays financial transaction metadata (confirmation status of charges) but does not move money, create obligations, modify records, or execute operations. It is a read-only query into a financial ledger. While it accesses financial data, the read category takes precedence over financial category per the severity hierarchy—no money or obligations change.
From the tool's definition Lists pending charge confirmations and their status without modifying data. Filters by client or confirmation status (pending, confirmed, disputed, auto_confirmed). The action is purely informational retrieval with 'list' semantics and no side effects.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs finance_list_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_list_confirmations, this is the rule to start with:
finance_list_confirmations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every finance_list_confirmations call is checked against it from then on.
Questions about finance_list_confirmations
List pending charge confirmations and their status. Shows cobros in pending_confirmation state that await client verification. Filter by client or confirmation status (pending, confirmed, disputed, auto_confirmed). It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
finance_list_confirmations accepts 4 parameters: apiKey, status, orgSlug, clientId. Required: 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_list_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_list_confirmations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the finance_list_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_list_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_list_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.
This server
Across the catalogue