create_whatsapp_connect_link
Create a short-lived browser link for WhatsApp Business Embedded Signup. The user must open the link because Meta requires a browser popup to authorize and choose the WABA/phone number.
This record as markdown: /tools/io-favcrm-favcrm/create-whatsapp-connect-link.md
What create_whatsapp_connect_link does on FavCRM
AI agents use create_whatsapp_connect_link 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 |
|---|---|---|---|
ttlMinutes | integer | — | Connect link lifetime in minutes. Defaults to 30. |
onboardingMode | string | — | Use cloud_api for a new WhatsApp Cloud API connection, or coexistence when connecting a WhatsApp Business App number. |
Parameters from the server's own tool schema.
Why create_whatsapp_connect_link is rated Medium
The tool creates a short-lived link to initiate WhatsApp Business account connection. This is a Write action (creating a resource/link), not merely reading data. Misuse could lead to unauthorized WhatsApp Business account linking attempts, but the actual authorization still requires user interaction in a browser popup, limiting blast radius somewhat.
From the tool's definition 'Create a short-lived browser link for WhatsApp Business Embedded Signup' — creates a link/resource, initiating an OAuth-style authorization flow
Attacks that exploit this kind of access
The rule that runs create_whatsapp_connect_link 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_whatsapp_connect_link, this is the rule to start with:
create_whatsapp_connect_link 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_whatsapp_connect_link call is checked against it from then on.
Questions about create_whatsapp_connect_link
Create a short-lived browser link for WhatsApp Business Embedded Signup. The user must open the link because Meta requires a browser popup to authorize and choose the WABA/phone number. 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_whatsapp_connect_link accepts 2 parameters: ttlMinutes, onboardingMode. 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_whatsapp_connect_link: 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_whatsapp_connect_link 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_whatsapp_connect_link 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_whatsapp_connect_link. 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_whatsapp_connect_link 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