happ_crm_sync_enable
Включить зеркалирование подключённой CRM в Happ: стартует первичный импорт (справочники → контакты → лиды → сделки), дальше дельта каждые несколько минут. Одна компания — одна CRM. companyIntegrationId — из happ_integrations_list (только CRM, которые поддерживает хаб — см. supportedTypes в happ_c...
This record as markdown: /tools/happ-ai-platform-mcp/happ-crm-sync-enable.md
What happ_crm_sync_enable does on Platform
AI agents use happ_crm_sync_enable to create or update resources in Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Platform environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
direction | string | — | two_way (по умолчанию): созданное на платформе уезжает в CRM; pull_only — только читаем |
crmDataConsent | boolean | — | true — пользователь ТОЛЬКО ЧТО явно согласился, что Happ получает и хранит данные этой CRM; записывается на интеграцию перед включением. Без явного ответа польз |
companyIntegrationId | string | Yes |
Parameters from the server's own tool schema.
Why happ_crm_sync_enable is rated Medium
An AI agent can call happ_crm_sync_enable faster than any human can review: one bad instruction and it creates or modifies resources in Platform by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs happ_crm_sync_enable 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_sync_enable, this is the rule to start with:
happ_crm_sync_enable 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 Platform, apply this rule, and every happ_crm_sync_enable call is checked against it from then on.
Questions about happ_crm_sync_enable
Включить зеркалирование подключённой CRM в Happ: стартует первичный импорт (справочники → контакты → лиды → сделки), дальше дельта каждые несколько минут. Одна компания — одна CRM. companyIntegrationId — из happ_integrations_list (только CRM, которые поддерживает хаб — см. supportedTypes в happ_crm_schema). ТРЕБУЕТ согласия компании на получение и хранение её CRM-данных в Happ: если в карточке интеграции (config.crmDataConsent.accepted) его нет — СНАЧАЛА спроси пользователя прямым вопросом («Вы даёте Happ согласие получать и хранить данные вашей CRM — контакты, сделки, лиды, активности? Без согласия синхронизация невозможна») и только при явном «да» передай crmDataConsent=true. Не выставляй согласие сам. (POST /crm/mirroring). It is categorised as a Write tool in the Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
happ_crm_sync_enable accepts 3 parameters: direction, crmDataConsent, companyIntegrationId. Required: companyIntegrationId. 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_crm_sync_enable: 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_crm_sync_enable 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 happ_crm_sync_enable 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_crm_sync_enable. 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_crm_sync_enable 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