set_resource_availability
Add an availability window for a resource. Use day-of-week + recurring=true for weekly schedules, or a specific date for one-off blocks.
This record as markdown: /tools/io-favcrm-favcrm/set-resource-availability.md
What set_resource_availability does on FavCRM
AI agents use set_resource_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) |
dayOfWeek | string | — | Day of week (0=Sun..6=Sat) |
startTime | string | Yes | HH:MM (24h) |
resourceId | string | Yes | Resource ID |
isRecurring | boolean | — | Default true |
Parameters from the server's own tool schema.
Why set_resource_availability is rated Medium
This tool creates or modifies schedule/availability data for a resource (person, service, or facility) in the CRM. It is reversible — availability windows can be updated or removed later — and does not delete data or trigger external operations. It fits the Write category: creates or modifies data reversibly.
From the tool's definition Tool description states it will 'Add an availability window' — the verb 'Add' denotes creation of a new scheduling record. The parameters reference 'day-of-week', 'recurring', and 'date', all of which are attributes being written to a resource schedule.
Attacks that exploit this kind of access
The rule that runs set_resource_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_resource_availability, this is the rule to start with:
set_resource_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_resource_availability call is checked against it from then on.
Questions about set_resource_availability
Add an availability window for a resource. Use day-of-week + recurring=true for weekly schedules, or a specific date for one-off blocks. 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_resource_availability accepts 7 parameters: date, type, endTime, dayOfWeek, startTime, resourceId, isRecurring. Required: endTime, startTime, 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 set_resource_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_resource_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_resource_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_resource_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_resource_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