create_resource
Create a bookable resource (room, equipment, vehicle). Used by services that have requiresResource=true.
This record as markdown: /tools/io-favcrm-favcrm/create-resource.md
What create_resource does on FavCRM
AI agents use create_resource 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 |
|---|---|---|---|
name | string | Yes | Resource name (e.g. "Treatment Room A") |
type | string | Yes | Free-form type label, e.g. "room", "equipment" |
status | string | — | Default active |
capacity | number | — | How many concurrent bookings (default 1) |
description | string | — | Description |
Parameters from the server's own tool schema.
Why create_resource is rated Medium
This is a Write operation as it creates and adds new data (resources) to the system that can be modified or removed later. It is not Destructive because resource creation is reversible. It is not Financial or Execute—no money moves and no arbitrary code runs.
From the tool's definition The tool 'create_resource' explicitly creates a new bookable resource (room, equipment, vehicle) in the CRM system.
Attacks that exploit this kind of access
The rule that runs create_resource 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 create_resource, this is the rule to start with:
create_resource 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 create_resource call is checked against it from then on.
Questions about create_resource
Create a bookable resource (room, equipment, vehicle). Used by services that have requiresResource=true. 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.
create_resource accepts 5 parameters: name, type, status, capacity, description. Required: name, type. 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 create_resource: 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.
create_resource 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 create_resource 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 create_resource. 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.
create_resource 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