set_staff_availability
Add an availability window for a staff member (companyMembers.id). Use day-of-week + recurring for weekly schedules, or a specific date for one-off changes.
This record as markdown: /tools/io-favcrm-favcrm/set-staff-availability.md
What set_staff_availability does on FavCRM
AI agents use set_staff_availability 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 | — | YYYY-MM-DD for a specific date instead of dayOfWeek |
type | string | — | Default available |
endTime | string | Yes | HH:MM (24h) |
memberId | string | Yes | companyMembers.id of the staff |
dayOfWeek | string | — | Day of week (0=Sun..6=Sat) |
startTime | string | Yes | HH:MM (24h) |
isRecurring | boolean | — | Default true |
Parameters from the server's own tool schema.
Why set_staff_availability is rated Medium
This tool creates or modifies staff availability records, which are reversible changes to scheduling metadata. It does not execute commands, delete data, move money, or cause irreversible effects. It is purely a data write operation typical of a CRM's scheduling functionality.
From the tool's definition Tool description states 'Add an availability window' — this is a create/modify operation that adds scheduling data. The parameters include staff member ID and availability windows (day-of-week, recurring, or specific dates).
Attacks that exploit this kind of access
The rule that runs set_staff_availability 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 set_staff_availability, this is the rule to start with:
set_staff_availability 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 set_staff_availability call is checked against it from then on.
Questions about set_staff_availability
Add an availability window for a staff member (companyMembers.id). Use day-of-week + recurring for weekly schedules, or a specific date for one-off changes. 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.
set_staff_availability accepts 7 parameters: date, type, endTime, memberId, dayOfWeek, startTime, isRecurring. Required: endTime, memberId, startTime. 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 set_staff_availability: 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.
set_staff_availability 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 set_staff_availability 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 set_staff_availability. 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.
set_staff_availability 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