client_list
List clients of an organization with search and pagination. Can filter by provider or outstanding debt.
This record as markdown: /tools/com-servicialo-mcp-server/client-list.md
What client_list does on Servicialo
AI agents call client_list 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 |
|---|---|---|---|
limit | integer | — | |
apiKey | string | — | |
cursor | string | — | |
search | string | — | |
hasDebt | boolean | — | |
orgSlug | string | Yes | |
providerId | string | — |
Parameters from the server's own tool schema.
Why client_list is rated Low
This tool retrieves and queries client information with optional filtering. It has no side effects, does not modify data, and does not trigger external operations. It is purely informational/read-only access, making it a Read category tool with low severity despite potential exposure of sensitive financial data (outstanding debt filtering), as the risk depends on authentication/authorization controls outside this…
From the tool's definition Tool name 'client_list' and description 'List clients of an organization with search and pagination' indicate a retrieval operation. The ability to filter by provider or outstanding debt does not alter data, only queries existing records.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs client_list 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 client_list, this is the rule to start with:
client_list 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 client_list call is checked against it from then on.
Questions about client_list
List clients of an organization with search and pagination. Can filter by provider or outstanding debt. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
client_list accepts 7 parameters: limit, apiKey, cursor, search, hasDebt, orgSlug, providerId. 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 client_list: 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.
client_list 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 client_list 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 client_list. 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.
client_list 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