comms_update_preferences

Enable or disable communication channels and features for an organization. Partial update — only provided fields are changed. Creates preferences if none exist.

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 121 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/comms-update-preferences.md

WHAT IT DOES

What comms_update_preferences does on Servicialo

AI agents use comms_update_preferences 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
`apiKey`	string	—
`orgSlug`	string	Yes
`emailEnabled`	boolean	—
`phoneRequired`	boolean	—
`whatsappEnabled`	boolean	—
`emailReminderEnabled`	boolean	—
`phoneRequiredMessage`	string	—
`whatsappReminderEnabled`	boolean	—
`whatsappReminderMessage`	string	—
`emailConfirmationEnabled`	boolean	—
`whatsappConfirmationEnabled`	boolean	—
`whatsappConfirmationMessage`	string	—

Parameters from the server's own tool schema.

RISK

Why comms_update_preferences is rated Medium

Modifies organization communication settings reversibly; creates preferences if absent.

From the tool's definition Enable or disable communication channels, partial update, creates preferences.

Risk signalsHandles credentials or secrets (apiKey) · High parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs comms_update_preferences 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 comms_update_preferences, this is the rule to start with:

comms_update_preferences Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "comms_update_preferences": {
      "limits": [
        {
          "counter": "comms_update_preferences_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every comms_update_preferences call is checked against it from then on.

FAQ

Questions about comms_update_preferences

What does the comms_update_preferences tool do? +

Enable or disable communication channels and features for an organization. Partial update — only provided fields are changed. Creates preferences if none exist. 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 comms_update_preferences accept? +

comms_update_preferences accepts 12 parameters: apiKey, orgSlug, emailEnabled, phoneRequired, whatsappEnabled, emailReminderEnabled, phoneRequiredMessage, whatsappReminderEnabled, whatsappReminderMessage, emailConfirmationEnabled, whatsappConfirmationEnabled, whatsappConfirmationMessage. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on comms_update_preferences? +

Register the Servicialo MCP server in PolicyLayer and add a rule for comms_update_preferences: 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 comms_update_preferences? +

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

Can I rate-limit comms_update_preferences? +

Yes. Add a rate_limit block to the comms_update_preferences 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 comms_update_preferences completely? +

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

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

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →