client_update
Update an existing client's personal data. Email cannot be changed via MCP.
This record as markdown: /tools/com-servicialo-mcp-server/client-update.md
What client_update does on Servicialo
AI agents use client_update to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rut | string | — | |
name | string | — | |
notes | string | — | |
phone | string | — | |
apiKey | string | — | |
comuna | string | — | |
orgSlug | string | Yes | |
clientId | string | Yes | |
lastName | string | — | |
direccion | string | — | |
proveedorTitularId | string | — |
Parameters from the server's own tool schema.
Why client_update is rated Medium
This tool creates or modifies client data reversibly without deletion. While it accesses personal information (moderate sensitivity), the constraint that 'Email cannot be changed via MCP' suggests appropriate safeguards are in place. The impact is limited to updating individual client records rather than bulk operations or irreversible destruction.
From the tool's definition Tool name 'client_update' and description 'Update an existing client's personal data' indicate modification of existing data records.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs client_update 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_update, this is the rule to start with:
client_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_update call is checked against it from then on.
Questions about client_update
Update an existing client's personal data. Email cannot be changed via MCP. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
client_update accepts 11 parameters: rut, name, notes, phone, apiKey, comuna, orgSlug, clientId, lastName, direccion, proveedorTitularId. Required: orgSlug, 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 client_update: 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_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the client_update 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_update. 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_update 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