finance_list_payments
List payments received with filters. Includes summary by payment type.
This record as markdown: /tools/com-servicialo-mcp-server/finance-list-payments.md
What finance_list_payments does on Servicialo
AI agents call finance_list_payments 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 |
|---|---|---|---|
tipo | string | — | |
limit | integer | — | |
apiKey | string | — | |
cursor | string | — | |
dateTo | string | — | |
orgSlug | string | Yes | |
clientId | string | — | |
dateFrom | string | — |
Parameters from the server's own tool schema.
Why finance_list_payments is rated Low
This tool queries and retrieves payment data with optional filtering and summarization. There is no indication it modifies, deletes, or moves money. The blast radius of misuse is low—an AI agent could potentially enumerate payment records or infer financial patterns, but cannot execute transfers, delete payments, or create financial obligations. This is a straightforward Read operation.
From the tool's definition Tool name contains 'list' and description states 'List payments received with filters. Includes summary by payment type.' The verb 'list' and lack of any modification language indicate a read-only operation that retrieves payment records without altering them.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs finance_list_payments 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_payments, this is the rule to start with:
finance_list_payments 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_payments call is checked against it from then on.
Questions about finance_list_payments
List payments received with filters. Includes summary by payment type. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
finance_list_payments accepts 8 parameters: tipo, limit, apiKey, cursor, dateTo, orgSlug, clientId, dateFrom. 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_payments: 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_payments 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_payments 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_payments. 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_payments 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