create_whatsapp_template

Створити WhatsApp-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 74 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/create-whatsapp-template.md

WHAT IT DOES

What create_whatsapp_template does on QuintaDB

AI agents use create_whatsapp_template to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.

Parameter	Type	Required	Description
`body`	string	Yes	Текст повідомлення (використовуй html_name полів без дужок)
`name`	string	Yes	Display name
`app_id`	string	Yes	Project ID (from list_projects)
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`channel_id`	string	—	ID WhatsApp-каналу (q_channel). Якщо не вказано — береться перший підключений канал проєкту.
`message_type`	string	—	Тип шаблону WhatsApp
`language_code`	string	—	Код мови, напр. en_US, uk

Parameters from the server's own tool schema.

RISK

Why create_whatsapp_template is rated Medium

This tool creates (writes) WhatsApp message templates that can be stored and reused. While template creation is reversible (templates can typically be edited or deleted), it modifies the system state by persisting new template definitions.

From the tool's definition Tool name 'create_whatsapp_template' and description indicate creation of a WhatsApp message template. The verb 'Створити' (create) and instruction to insert form fields into template body clearly indicate data creation/modification.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_whatsapp_template safely

PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_whatsapp_template, this is the rule to start with:

create_whatsapp_template Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_whatsapp_template": {
      "limits": [
        {
          "counter": "create_whatsapp_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every create_whatsapp_template call is checked against it from then on.

FAQ

Questions about create_whatsapp_template

What does the create_whatsapp_template tool do? +

Створити WhatsApp-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_whatsapp_template accept? +

create_whatsapp_template accepts 7 parameters: body, name, app_id, entity_id, channel_id, message_type, language_code. Required: body, name, app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_whatsapp_template? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for create_whatsapp_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 QuintaDB. Nothing to install.

What risk level is create_whatsapp_template? +

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

Can I rate-limit create_whatsapp_template? +

Yes. Add a rate_limit block to the create_whatsapp_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_whatsapp_template completely? +

Set action: deny in the PolicyLayer policy for create_whatsapp_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_whatsapp_template? +

create_whatsapp_template is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 116 QuintaDB tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →