update_service_schedule
Update a service schedule window. Pass only fields to change.
This record as markdown: /tools/io-favcrm-favcrm/update-service-schedule.md
What update_service_schedule does on FavCRM
AI agents use update_service_schedule to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | Date (YYYY-MM-DD) |
notes | object | — | Free-form notes |
endTime | string | — | End time (HH:mm) |
staffId | object | — | Staff member ID |
byWeekday | object | — | Weekdays (0=Mon..6=Sun) for weekly recurrence |
startTime | string | — | Start time (HH:mm) |
recurrence | string | — | Recurrence rule: none | daily | weekly | monthly |
resourceId | object | — | Resource ID (room/equipment) |
scheduleId | string | Yes | Schedule ID |
maxCapacity | number | — | Maximum capacity for this slot |
recurrenceEndDate | object | — | Recurrence end date (YYYY-MM-DD) |
recurrenceInterval | number | — | Recurrence interval (e.g. every N weeks) |
Parameters from the server's own tool schema.
Why update_service_schedule is rated Medium
This tool modifies existing service schedule records reversibly—a core CRM operation for a service business. It creates or changes data without permanently deleting or executing external code.
From the tool's definition Tool name 'update_service_schedule' and description 'Update a service schedule window. Pass only fields to change.' indicate modification of schedule data.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs update_service_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_service_schedule, this is the rule to start with:
update_service_schedule 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 FavCRM, apply this rule, and every update_service_schedule call is checked against it from then on.
Questions about update_service_schedule
Update a service schedule window. Pass only fields to change. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_service_schedule accepts 12 parameters: date, notes, endTime, staffId, byWeekday, startTime, recurrence, resourceId, scheduleId, maxCapacity, recurrenceEndDate, recurrenceInterval. Required: scheduleId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for update_service_schedule: 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 FavCRM. Nothing to install.
update_service_schedule 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 update_service_schedule 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 update_service_schedule. 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.
update_service_schedule is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue