happ_call_originate
РЕАЛЬНЫЙ исходящий телефонный звонок голосового ассистента на номер клиента . Запускай ТОЛЬКО по явной просьбе человека и с подтверждённым им номером — звонок платный (SIP + LLM), отменить после запуска нельзя. Требования: у ассистента подключён телефон, у компании активная подписка и SIP-баланс....
This record as markdown: /tools/happ-ai-platform-mcp/happ-call-originate.md
What happ_call_originate does on Platform
AI agents call happ_call_originate to retrieve information from Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
assistantId | string | Yes | ID голосового ассистента, который звонит |
phoneNumber | string | Yes | Номер клиента: +380..., цифры с кодом страны или локальный с 0 |
dynamicVariables | object | — | Значения {{плейсхолдеров}} промпта для этого звонка (customer_name, order_id...) |
callerAssistantId | string | — | Звонить от имени ДРУГОГО ассистента той же компании (по умолчанию — ассистент из assistantId) |
Parameters from the server's own tool schema.
Why happ_call_originate is rated Low
Even though happ_call_originate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs happ_call_originate 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_call_originate, this is the rule to start with:
happ_call_originate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_call_originate call is checked against it from then on.
Questions about happ_call_originate
РЕАЛЬНЫЙ исходящий телефонный звонок голосового ассистента на номер клиента . Запускай ТОЛЬКО по явной просьбе человека и с подтверждённым им номером — звонок платный (SIP + LLM), отменить после запуска нельзя. Требования: у ассистента подключён телефон, у компании активная подписка и SIP-баланс. dynamicVariables подставляют {{плейсхолдеры}} промпта на время звонка (имя клиента, номер заказа и т.п.). Возвращает workflowId; сам звонок появится в happ_calls_list после завершения. (POST /assistants/:assistantId/originate). It is categorised as a Read tool in the Platform MCP Server, which means it retrieves data without modifying state.
happ_call_originate accepts 4 parameters: assistantId, phoneNumber, dynamicVariables, callerAssistantId. Required: assistantId, phoneNumber. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_call_originate: 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.
happ_call_originate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the happ_call_originate 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 happ_call_originate. 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.
happ_call_originate 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.
More on Platform, and thousands of servers like it.
This server
Across the catalogue