reminders_update_config

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 91 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/reminders-update-config.md

WHAT IT DOES

What reminders_update_config does on Servicialo

AI agents use reminders_update_config 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
`paymentOverdue`	object	—
`bookingReminder`	object	—
`paymentReminder`	object	—
`sessionReminder1h`	object	—
`sessionReminder24h`	object	—
`pendingConfirmation`	object	—
`notificationFollowup`	object	—

Parameters from the server's own tool schema.

RISK

Why reminders_update_config is rated Medium

Modifies organizational notification settings reversibly without data deletion or financial impact.

From the tool's definition Update reminder/notification configuration for an organization. Partial update.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reminders_update_config Rate-limited

reminders_update_config 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": {
    "reminders_update_config": {
      "limits": [
        {
          "counter": "reminders_update_config_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 reminders_update_config call is checked against it from then on.

FAQ

Questions about reminders_update_config

What does the reminders_update_config tool do? +

Update reminder/notification configuration for an organization. Partial update — only provided sections are changed. Sections: bookingReminder {enabled, daysAfter, maxReminders, interval}, sessionReminder24h {enabled, hoursBefore, sendTime}, sessionReminder1h {enabled, hoursBefore}, paymentReminder {enabled, daysAfter, maxReminders, interval}, paymentOverdue {enabled, daysOverdue, maxReminders, interval}, notificationFollowup {enabled, daysAfter, maxFollowups, interval}, pendingConfirmation {enabled, cutoffHours, autoConfirm} (cutoffHours = hours BEFORE the appointment that an unaccepted booking expires). Returns the full configuration after update. 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 reminders_update_config accept? +

reminders_update_config accepts 9 parameters: apiKey, orgSlug, paymentOverdue, bookingReminder, paymentReminder, sessionReminder1h, sessionReminder24h, pendingConfirmation, notificationFollowup. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reminders_update_config? +

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

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

Can I rate-limit reminders_update_config? +

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

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

reminders_update_config 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 →reminders_complete on Apple Apps MCP → The MCP Attack Database →

Guides

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