create_template
Create and submit a WhatsApp message template to Meta for approval. Text templates only (header text, body with {{1}} variables, footer) — add buttons in the app. The template is NOT usable until Meta approves it (check with list_templates). Submitting consumes the store’s Meta template allowance.
This record as markdown: /tools/io-favcrm-favcrm/create-template.md
What create_template does on FavCRM
AI agents use create_template 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 | Friendly template name (a Meta-safe id is derived from it). |
footer | string | — | Optional small footer text. |
message | string | Yes | Body text. Use {{1}}, {{2}} for personalised values. |
category | string | Yes | UTILITY = transactional (order/shipping), MARKETING = promos, AUTHENTICATION = codes. |
language | string | — | Language code, default en_US. |
headerText | string | — | Optional short bold header above the body. |
variableSamples | object | — | Example values per variable number, e.g. {"1":"Sara"} — Meta reviews with these. |
Parameters from the server's own tool schema.
Why create_template is rated Medium
This tool creates a new resource (WhatsApp message template) and modifies the store's template quota/allowance by consuming one submission. These are reversible write operations — templates can be deleted or resubmitted, and the allowance is a tracking counter. It does not execute arbitrary code, delete irreversibly, handle financial transactions, or run external commands directly.
From the tool's definition Tool creates and submits a WhatsApp message template to Meta for approval. The template is created in the system and submitted to an external service (Meta), which consumes the store's Meta template allowance.
Attacks that exploit this kind of access
The rule that runs create_template 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_template, this is the rule to start with:
create_template 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_template call is checked against it from then on.
Questions about create_template
Create and submit a WhatsApp message template to Meta for approval. Text templates only (header text, body with {{1}} variables, footer) — add buttons in the app. The template is NOT usable until Meta approves it (check with list_templates). Submitting consumes the store’s Meta template allowance. 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_template accepts 7 parameters: name, footer, message, category, language, headerText, variableSamples. Required: name, message, category. 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_template: 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_template 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_template 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_template. 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_template 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