get_available_slots
Find available booking slots for a service on a specific date.
This record as markdown: /tools/io-favcrm-favcrm/get-available-slots.md
What get_available_slots does on FavCRM
AI agents call get_available_slots 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 |
|---|---|---|---|
date | string | Yes | ISO date to check (YYYY-MM-DD) |
staffId | string | — | Optional: filter by specific staff member |
serviceId | string | Yes | The service to check availability for |
resourceId | string | — | Optional: filter by specific resource |
Parameters from the server's own tool schema.
Why get_available_slots is rated Low
This tool retrieves scheduling information to display available time slots. It performs a query operation without creating, modifying, deleting, or executing any actions. The data returned is informational only and used to inform booking decisions rather than commit them. No irreversible changes or external operations are triggered.
From the tool's definition The tool 'get_available_slots' is described as finding or querying available booking slots for a service on a specific date. The verb 'find' and the function name 'get_' indicate data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs get_available_slots 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 get_available_slots, this is the rule to start with:
get_available_slots 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 get_available_slots call is checked against it from then on.
Questions about get_available_slots
Find available booking slots for a service on a specific date. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_available_slots accepts 4 parameters: date, staffId, serviceId, resourceId. Required: date, serviceId. 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 get_available_slots: 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.
get_available_slots 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 get_available_slots 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 get_available_slots. 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.
get_available_slots 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