happ_crm_call_trigger_create

SERVERPlatform SOURCE@happ-ai/platform-mcp

High RISK CLASS

Category Execute

Parameters 114 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/happ-ai-platform-mcp/happ-crm-call-trigger-create.md

WHAT IT DOES

What happ_crm_call_trigger_create does on Platform

AI agents invoke happ_crm_call_trigger_create to trigger actions in Platform. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`name`	string	Yes	Название триггера, например «Новый лид → перезвонить»
`queueId`	string	Yes	Очередь обзвона, в которую попадут номера (владеет расписанием и лимитами)
`isActive`	boolean	—	Сразу включить (по умолчанию да)
`companyId`	string	Yes	ID компании
`dedupDays`	integer	—	Не звонить тому же номеру повторно N дней
`matchPath`	string	—	Путь к стадии в событии (guide.stagePath); по умолчанию из setup
`phonePath`	string	—	Путь к телефону клиента (guide.phonePath); по умолчанию из setup
`matchValue`	string	—	Стадия/значение, при котором звонить (stage.value из setup); пусто = любое событие
`templateId`	string	—	Готовый сценарий — тогда стадия и переменные подберутся сами
`variableMappings`	array	—	Какие поля события подставлять в промпт как {{переменные}}; по умолчанию все поля из setup
`companyIntegrationId`	string	Yes	ID подключённой CRM

Parameters from the server's own tool schema.

RISK

Why happ_crm_call_trigger_create is rated High

happ_crm_call_trigger_create triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (variableMappings[].path) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs happ_crm_call_trigger_create safely

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

happ_crm_call_trigger_create Rate-limited

happ_crm_call_trigger_create stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "happ_crm_call_trigger_create": {
      "limits": [
        {
          "counter": "happ_crm_call_trigger_create_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about happ_crm_call_trigger_create

What does the happ_crm_call_trigger_create tool do? +

Создаёт триггер: при событии CRM (стадия лида/сделки) номер клиента попадает в очередь обзвона, и голосовой ассистент звонит. Нужна подключённая CRM и очередь обзвона (лучше бесконечная, isContinuous). Стадию и пути полей бери из happ_crm_call_trigger_setup; если matchPath/phonePath/variableMappings не переданы — подставятся из setup автоматически. (POST /crm-call-triggers). It is categorised as a Execute tool in the Platform MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does happ_crm_call_trigger_create accept? +

happ_crm_call_trigger_create accepts 11 parameters: name, queueId, isActive, companyId, dedupDays, matchPath, phonePath, matchValue, templateId, variableMappings, companyIntegrationId. Required: name, queueId, companyId, companyIntegrationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on happ_crm_call_trigger_create? +

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

What risk level is happ_crm_call_trigger_create? +

happ_crm_call_trigger_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit happ_crm_call_trigger_create? +

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

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

happ_crm_call_trigger_create is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Platform, and thousands of servers like it.

This server

All 275 Platform tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt →diagram_create on Templonix Lite MCP Server →call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →