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.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp
Medium RISK CLASS
Category Write
Parameters 73 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about create_template

What does the create_template tool do? +

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.

What parameters does create_template accept? +

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.

How do I enforce a policy on create_template? +

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.

What risk level is create_template? +

create_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_template? +

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.

How do I block create_template completely? +

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.

What MCP server provides create_template? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FavCRM's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.