cierre_crear_cliente
Create a client monthly closing (immutable financial snapshot). Requires historialCompleto=true on the client. One closing per client per period. Requires confirm: true.
This record as markdown: /tools/com-servicialo-mcp-server/cierre-crear-cliente.md
What cierre_crear_cliente does on Servicialo
AI agents use cierre_crear_cliente 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 |
|---|---|---|---|
notas | string | — | |
apiKey | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
periodo | string | Yes | |
clientId | string | Yes |
Parameters from the server's own tool schema.
Why cierre_crear_cliente is rated Critical
This tool creates an immutable financial snapshot (monthly closing) for a client. The financial nature is explicit ('financial snapshot'), and immutability means it cannot be undone, making it both Financial and effectively Destructive in terms of reversibility. Financial takes precedence as the highest severity category.
From the tool's definition 'Create a client monthly closing (immutable financial snapshot)' and 'Requires confirm: true' — creates a financial record that is explicitly immutable once created
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs cierre_crear_cliente 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_crear_cliente, this is the rule to start with:
Any call to cierre_crear_cliente 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 cierre_crear_cliente call is checked against it from then on.
Questions about cierre_crear_cliente
Create a client monthly closing (immutable financial snapshot). Requires historialCompleto=true on the client. One closing per client per period. 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.
cierre_crear_cliente accepts 6 parameters: notas, apiKey, confirm, orgSlug, periodo, clientId. Required: confirm, orgSlug, periodo, clientId. 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_crear_cliente: 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_crear_cliente 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 cierre_crear_cliente 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_crear_cliente. 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_crear_cliente 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