cierre_cerrar_org
Close the organizational period. Requires ALL active clients with historialCompleto=true to be closed first. Freezes the period. Requires confirm: true.
This record as markdown: /tools/com-servicialo-mcp-server/cierre-cerrar-org.md
What cierre_cerrar_org does on Servicialo
AI agents call cierre_cerrar_org to permanently remove resources in Servicialo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
periodo | string | Yes |
Parameters from the server's own tool schema.
Why cierre_cerrar_org is rated Critical
Closing and freezing an organizational period is an irreversible administrative action. Once a period is frozen, historical records are locked and cannot be modified. The requirement for explicit confirmation ('confirm: true') and pre-conditions (all active clients must be closed first) underscores its irreversible, high-impact nature, making it Destructive with critical severity.
From the tool's definition 'Close the organizational period', 'Freezes the period', 'Requires confirm: true'
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs cierre_cerrar_org 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_cerrar_org, this is the rule to start with:
cierre_cerrar_org is removed from the agent's tool list entirely, so the agent never calls 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_cerrar_org call is checked against it from then on.
Questions about cierre_cerrar_org
Close the organizational period. Requires ALL active clients with historialCompleto=true to be closed first. Freezes the period. Requires confirm: true. It is categorised as a Destructive tool in the Servicialo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cierre_cerrar_org accepts 4 parameters: apiKey, confirm, orgSlug, periodo. Required: confirm, orgSlug, periodo. 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_cerrar_org: 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_cerrar_org is a Destructive 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_cerrar_org 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_cerrar_org. 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_cerrar_org 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