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

client_update

Update an existing client's personal data. Email cannot be changed via MCP.

SERVERServicialo SOURCE@servicialo/mcp-server
Medium RISK CLASS
Category Write
Parameters 112 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about client_update

What does the client_update tool do? +

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.

What parameters does client_update accept? +

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.

How do I enforce a policy on client_update? +

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.

What risk level is client_update? +

client_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit client_update? +

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.

How do I block client_update completely? +

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.

What MCP server provides client_update? +

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.

// 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.