list_service_schedules
List schedule windows for booking services.
This record as markdown: /tools/io-favcrm-favcrm/list-service-schedules.md
What list_service_schedules does on FavCRM
AI agents call list_service_schedules to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 20) |
dateTo | string | — | YYYY-MM-DD |
staffId | string | — | Staff member ID |
dateFrom | string | — | YYYY-MM-DD |
serviceId | string | — | Service ID |
isOverride | boolean | — | Filter to override entries only |
resourceId | string | — | Resource ID (room/equipment) |
Parameters from the server's own tool schema.
Why list_service_schedules is rated Low
This tool queries and returns schedule data for services without modifying, deleting, or executing any operations. It is a straightforward data retrieval function typical of CRM read operations. The low severity reflects minimal risk even if misused, as it only exposes scheduling information that would typically be accessible to authorized users anyway.
From the tool's definition Tool name 'list_service_schedules' and description 'List schedule windows for booking services' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_service_schedules 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 list_service_schedules, this is the rule to start with:
list_service_schedules is read-only, so it stays allowed. 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 list_service_schedules call is checked against it from then on.
Questions about list_service_schedules
List schedule windows for booking services. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_service_schedules accepts 7 parameters: limit, dateTo, staffId, dateFrom, serviceId, isOverride, resourceId. 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 list_service_schedules: 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.
list_service_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_service_schedules 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 list_service_schedules. 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.
list_service_schedules 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