settings_update
Update organization settings. Partial update — only provided keys are changed. Pass a settings object with key-value pairs (e.g. {"policies.noShowMaxStrikes": 3, "finances.clientPaymentTiming": "BEFORE"}). ALL values are validated before ANY is written: if one key fails, nothing changes — so rela...
This record as markdown: /tools/com-servicialo-mcp-server/settings-update.md
What settings_update does on Servicialo
AI agents use settings_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 |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
settings | object | Yes |
Parameters from the server's own tool schema.
Why settings_update is rated Medium
Modifies organization configuration reversibly; high blast radius due to financial and policy implications.
From the tool's definition Update organization settings. Partial update — only provided keys are changed.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs settings_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 settings_update, this is the rule to start with:
settings_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 settings_update call is checked against it from then on.
Questions about settings_update
Update organization settings. Partial update — only provided keys are changed. Pass a settings object with key-value pairs (e.g. {"policies.noShowMaxStrikes": 3, "finances.clientPaymentTiming": "BEFORE"}). ALL values are validated before ANY is written: if one key fails, nothing changes — so related keys can be sent together and either all land or none do. That matters for settings with invariants between them (the cancellation tiers, where the partial-charge window must sit closer to the appointment than the no-charge one) and for the SII tax profile, whose legally required fields must arrive in a single call the first time. Returns the full updated settings for the affected chapters. See settings_get for available keys, valid values and dependencies. 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.
settings_update accepts 3 parameters: apiKey, orgSlug, settings. Required: orgSlug, settings. 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 settings_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.
settings_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 settings_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 settings_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.
settings_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