New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

happ_conversations_list

Единая история чатов и звонков компании (раздел «История»): контакт, агент, канал, превью, дата, длительность и исход звонка. Фильтры по типу, агенту, каналу, датам, исходу и длительности; поиск по контакту; contactId — все диалоги конкретного человека из CRM-хаба. (GET /conversations)

SERVERPlatform SOURCE@happ-ai/platform-mcp
Low RISK CLASS
Category Read
Parameters 120 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/happ-ai-platform-mcp/happ-conversations-list.md

What happ_conversations_list does on Platform

AI agents call happ_conversations_list 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.

ParameterTypeRequiredDescription
skip integer —
sort string —
take integer — Размер страницы, по умолчанию 100 (максимум); в ответе totalCount — сколько всего
type string — Тип: все / чаты / звонки
dateTo string — ISO-дата конца
filter string — Выражение фильтра — то же, что экран держит в адресе (?filter=…): условия «поле:оператор:значение» через «;». Со страницы передавай КАК ЕСТЬ. Списки для in/betw
search string — Поиск по имени, телефону или нику контакта
sortBy string — Поле сортировки (по умолчанию date DESC)
agentId string — Фильтр по ассистенту
channel string — Канал: telegram, whatsapp, widget, playground, phone и т.п.
outcome string — Исход звонка (только для звонков)
dateFrom string — ISO-дата начала

Parameters from the server's own tool schema.

Why happ_conversations_list is rated Low

Even though happ_conversations_list 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.

Risk signalsHigh parameter count (17 properties)

Questions about happ_conversations_list

What does the happ_conversations_list tool do? +

Единая история чатов и звонков компании (раздел «История»): контакт, агент, канал, превью, дата, длительность и исход звонка. Фильтры по типу, агенту, каналу, датам, исходу и длительности; поиск по контакту; contactId — все диалоги конкретного человека из CRM-хаба. (GET /conversations). It is categorised as a Read tool in the Platform MCP Server, which means it retrieves data without modifying state.

What parameters does happ_conversations_list accept? +

happ_conversations_list accepts 12 parameters: skip, sort, take, type, dateTo, filter, search, sortBy, agentId, channel, outcome, dateFrom. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on happ_conversations_list? +

Register the Platform MCP server in PolicyLayer and add a rule for happ_conversations_list: 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_conversations_list? +

happ_conversations_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit happ_conversations_list? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Platform's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.