New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cierre_preview_cliente

Preview the financial snapshot for a client in a period WITHOUT creating the closing. Returns totals for ventas, cobros, pagos, sessions.

SERVERServicialo SOURCE@servicialo/mcp-server
Low RISK CLASS
Category Read
Parameters 43 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/cierre-preview-cliente.md

What cierre_preview_cliente does on Servicialo

AI agents call cierre_preview_cliente 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.

ParameterTypeRequiredDescription
apiKey string
orgSlug string Yes
periodo string Yes
clientId string Yes

Parameters from the server's own tool schema.

Why cierre_preview_cliente is rated Low

This tool retrieves and displays financial data (totals for sales, collections, payments, sessions) for preview purposes only. It explicitly does not create, modify, or persist any changes. The lack of side effects and read-only nature places it firmly in the Read category with low severity.

From the tool's definition Tool description states 'Preview the financial snapshot for a client in a period WITHOUT creating the closing.

Risk signalsHandles credentials or secrets (apiKey)

Questions about cierre_preview_cliente

What does the cierre_preview_cliente tool do? +

Preview the financial snapshot for a client in a period WITHOUT creating the closing. Returns totals for ventas, cobros, pagos, sessions. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.

What parameters does cierre_preview_cliente accept? +

cierre_preview_cliente accepts 4 parameters: apiKey, orgSlug, periodo, clientId. Required: orgSlug, periodo, clientId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cierre_preview_cliente? +

Register the Servicialo MCP server in PolicyLayer and add a rule for cierre_preview_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.

What risk level is cierre_preview_cliente? +

cierre_preview_cliente is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cierre_preview_cliente? +

Yes. Add a rate_limit block to the cierre_preview_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.

How do I block cierre_preview_cliente completely? +

Set action: deny in the PolicyLayer policy for cierre_preview_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.

What MCP server provides cierre_preview_cliente? +

cierre_preview_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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Servicialo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.