happ_crm_contacts_search
Контакты (клиенты) компании: поиск по имени, телефону, email; фильтры по тегу, источнику, менеджеру, «без активности N дней». Телефон можно в любом формате. Возвращает страницу с totalCount. (GET /crm/contacts)
This record as markdown: /tools/happ-ai-platform-mcp/happ-crm-contacts-search.md
What happ_crm_contacts_search does on Platform
AI agents call happ_crm_contacts_search 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 |
|---|---|---|---|
q | string | — | Имя, телефон или email |
tag | string | — | |
sort | string | — | |
limit | integer | — | Сколько записей вернуть (по умолчанию 50) |
offset | integer | — | Смещение для постраничного обхода |
source | string | — | |
ownerId | string | — | |
companyId | string | — | ID компании (можно не указывать, если у пользователя одна компания) |
noActivityDays | integer | — | Только контакты без активности дольше N дней |
Parameters from the server's own tool schema.
Why happ_crm_contacts_search is rated Low
Even though happ_crm_contacts_search 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_crm_contacts_search 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_contacts_search, this is the rule to start with:
happ_crm_contacts_search 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_crm_contacts_search call is checked against it from then on.
Questions about happ_crm_contacts_search
Контакты (клиенты) компании: поиск по имени, телефону, email; фильтры по тегу, источнику, менеджеру, «без активности N дней». Телефон можно в любом формате. Возвращает страницу с totalCount. (GET /crm/contacts). It is categorised as a Read tool in the Platform MCP Server, which means it retrieves data without modifying state.
happ_crm_contacts_search accepts 9 parameters: q, tag, sort, limit, offset, source, ownerId, companyId, noActivityDays. 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_contacts_search: 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_contacts_search 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_crm_contacts_search 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_contacts_search. 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_contacts_search 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