link_resource_to_service
Link a room/resource to a booking service.
This record as markdown: /tools/io-favcrm-favcrm/link-resource-to-service.md
What link_resource_to_service does on FavCRM
AI agents use link_resource_to_service 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 |
|---|---|---|---|
serviceId | string | Yes | Service ID |
resourceId | string | Yes | Resource ID |
Parameters from the server's own tool schema.
Why link_resource_to_service is rated Medium
This tool modifies CRM data by establishing a relationship between resources and services, which affects booking behavior and service configuration. While reversible (unlike Destructive actions), it represents a Write operation that can impact business operations if misused—an agent could link inappropriate resources to services or create conflicts.
From the tool's definition The tool "Link a room/resource to a booking service" creates or modifies a resource-to-service association. This is a data modification action that associates an existing resource with a service, reversible through unlinking or modification.
Attacks that exploit this kind of access
The rule that runs link_resource_to_service 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 link_resource_to_service, this is the rule to start with:
link_resource_to_service 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 link_resource_to_service call is checked against it from then on.
Questions about link_resource_to_service
Link a room/resource to a booking service. 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.
link_resource_to_service accepts 2 parameters: serviceId, resourceId. Required: serviceId, 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 link_resource_to_service: 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.
link_resource_to_service 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 link_resource_to_service 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 link_resource_to_service. 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.
link_resource_to_service 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