happ_integrations_catalog
Все интеграции, которые платформа умеет подключать (мессенджеры, CRM, телефония, вебхуки, уведомления, свои AI-ключи), по категориям; для каждой — как подключить: прямо здесь инструментом (connect=copilot, copilotTool) или в родном диалоге кабинета (connect=dialog, через ui_open_dialog connect_in...
This record as markdown: /tools/happ-ai-platform-mcp/happ-integrations-catalog.md
What happ_integrations_catalog does on Platform
AI agents call happ_integrations_catalog 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 |
|---|---|---|---|
category | string | — | Фильтр по категории |
companyId | string | — | ID компании — чтобы пометить уже подключённые |
Parameters from the server's own tool schema.
Why happ_integrations_catalog is rated Low
Even though happ_integrations_catalog 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_integrations_catalog 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_integrations_catalog, this is the rule to start with:
happ_integrations_catalog 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_integrations_catalog call is checked against it from then on.
Questions about happ_integrations_catalog
Все интеграции, которые платформа умеет подключать (мессенджеры, CRM, телефония, вебхуки, уведомления, свои AI-ключи), по категориям; для каждой — как подключить: прямо здесь инструментом (connect=copilot, copilotTool) или в родном диалоге кабинета (connect=dialog, через ui_open_dialog connect_integration). Если передан companyId — помечает уже подключённые. Это ответ на «какие интеграции/CRM можно подключить»; happ_integrations_list показывает только подключённые. It is categorised as a Read tool in the Platform MCP Server, which means it retrieves data without modifying state.
happ_integrations_catalog accepts 2 parameters: category, companyId. 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_integrations_catalog: 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_integrations_catalog 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_integrations_catalog 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_integrations_catalog. 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_integrations_catalog 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