list_bookings
List bookings with filters for date range, status, service, staff, or member.
This record as markdown: /tools/io-favcrm-favcrm/list-bookings.md
What list_bookings does on FavCRM
AI agents call list_bookings 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 | — | ISO date — bookings up to this date |
status | string | — | Filter by booking status |
staffId | string | — | Filter by staff member ID |
dateFrom | string | — | ISO date — bookings from this date |
accountId | string | — | Filter by member/account ID |
serviceId | string | — | Filter by service ID |
Parameters from the server's own tool schema.
Why list_bookings is rated Low
This tool retrieves and queries booking data based on various filters (date range, status, service, staff, member). It has no side effects, does not create, modify, or delete data, and does not execute external operations or trigger financial transactions. It is a straightforward read operation typical of CRM data lookup functionality.
From the tool's definition Tool name is 'list_bookings' and description states it 'List bookings with filters' — a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs list_bookings 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_bookings, this is the rule to start with:
list_bookings 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_bookings call is checked against it from then on.
Questions about list_bookings
List bookings with filters for date range, status, service, staff, or member. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_bookings accepts 7 parameters: limit, dateTo, status, staffId, dateFrom, accountId, 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 list_bookings: 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_bookings 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_bookings 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_bookings. 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_bookings 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