cierre_listar_clientes
List client closings for an organization. Filter by period and/or client.
This record as markdown: /tools/com-servicialo-mcp-server/cierre-listar-clientes.md
What cierre_listar_clientes does on Servicialo
AI agents call cierre_listar_clientes 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 | — | |
orgSlug | string | Yes | |
periodo | string | — | |
clientId | string | — |
Parameters from the server's own tool schema.
Why cierre_listar_clientes is rated Low
This tool retrieves and queries existing client closing data without creating, modifying, or deleting records. However, 'closings' in a professional service delivery context likely refers to financial settlement or project completion records that could be sensitive business information.
From the tool's definition Tool name 'cierre_listar_clientes' and description 'List client closings for an organization. Filter by period and/or client.' indicate data retrieval with no modification capability. The verb 'list' and 'filter' are read-only operations.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs cierre_listar_clientes 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 cierre_listar_clientes, this is the rule to start with:
cierre_listar_clientes 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 cierre_listar_clientes call is checked against it from then on.
Questions about cierre_listar_clientes
List client closings for an organization. Filter by period and/or client. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
cierre_listar_clientes accepts 4 parameters: apiKey, orgSlug, periodo, 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 cierre_listar_clientes: 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.
cierre_listar_clientes 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 cierre_listar_clientes 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 cierre_listar_clientes. 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.
cierre_listar_clientes 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