create_service_schedule

Create a bookable schedule window for a service, including recurring weekly/daily availability.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 124 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/create-service-schedule.md

WHAT IT DOES

What create_service_schedule does on FavCRM

AI agents use create_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	Yes	Start date or one-off date (YYYY-MM-DD)
`notes`	string	—	Free-form notes
`endTime`	string	Yes	HH:MM (24h)
`staffId`	string	—	Optional companyMembers.id to bind this schedule to staff
`byWeekday`	array	—	Weekdays for weekly recurrence: 0=Mon, 1=Tue, ... 6=Sun
`serviceId`	string	Yes	Service ID
`startTime`	string	Yes	HH:MM (24h)
`recurrence`	string	—	Default none
`resourceId`	string	—	Optional resource ID to bind this schedule to a room/resource
`maxCapacity`	number	—	Max bookings per generated slot
`recurrenceEndDate`	string	—	YYYY-MM-DD
`recurrenceInterval`	number	—	Default 1

Parameters from the server's own tool schema.

RISK

Why create_service_schedule is rated Medium

This tool creates and stores new schedule data (recurring availability windows) in the CRM system. It modifies the system state by adding new bookable time slots. While it doesn't delete data or move money, it does persist new configuration that affects business operations. It is reversible (schedules can be modified or deleted), making it Write rather than Destructive.

From the tool's definition Tool creates a new bookable schedule window with recurring availability patterns. The description explicitly uses 'Create' and describes persistent configuration of service scheduling that can be modified or referenced by other systems.

Risk signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_service_schedule Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_service_schedule": {
      "limits": [
        {
          "counter": "create_service_schedule_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 FavCRM, apply this rule, and every create_service_schedule call is checked against it from then on.

FAQ

Questions about create_service_schedule

What does the create_service_schedule tool do? +

Create a bookable schedule window for a service, including recurring weekly/daily availability. 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.

What parameters does create_service_schedule accept? +

create_service_schedule accepts 12 parameters: date, notes, endTime, staffId, byWeekday, serviceId, startTime, recurrence, resourceId, maxCapacity, recurrenceEndDate, recurrenceInterval. Required: date, endTime, serviceId, startTime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_service_schedule? +

Register the FavCRM MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_service_schedule? +

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

Can I rate-limit create_service_schedule? +

Yes. Add a rate_limit block to the create_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.

How do I block create_service_schedule completely? +

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

What MCP server provides create_service_schedule? +

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

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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