happ_crm_pull_source_update

Меняет название, условия, расписание, дедупликацию или лимит pull-источника. CRM и очередь поменять нельзя — создай новый источник. (PATCH /crm-pull/sources/:id)

SERVERPlatform SOURCE@happ-ai/platform-mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/happ-ai-platform-mcp/happ-crm-pull-source-update.md

WHAT IT DOES

What happ_crm_pull_source_update does on Platform

AI agents use happ_crm_pull_source_update 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
`name`	string	—
`sourceId`	string	Yes	ID источника (happ_crm_pull_sources_list)
`dedupDays`	object	—	Не звонить повторно на номер, который уже был в очереди в последние N дней. Не указан — повторов не будет никогда
`conditions`	array	—
`scheduleTime`	object	—	Время суток HH:mm (в таймзоне кампании), когда запускать периодический импорт
`maxLeadsPerRun`	integer	—	Максимум записей за один прогон (по умолчанию 1000)
`intervalMinutes`	object	—	Повторять каждые N минут (30…10080). Не указан/null — разовый импорт

Parameters from the server's own tool schema.

RISK

Why happ_crm_pull_source_update is rated Medium

An AI agent can call happ_crm_pull_source_update 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.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs happ_crm_pull_source_update 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_pull_source_update, this is the rule to start with:

happ_crm_pull_source_update Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "happ_crm_pull_source_update": {
      "limits": [
        {
          "counter": "happ_crm_pull_source_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_crm_pull_source_update call is checked against it from then on.

FAQ

Questions about happ_crm_pull_source_update

What does the happ_crm_pull_source_update tool do? +

Меняет название, условия, расписание, дедупликацию или лимит pull-источника. CRM и очередь поменять нельзя — создай новый источник. (PATCH /crm-pull/sources/:id). 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.

What parameters does happ_crm_pull_source_update accept? +

happ_crm_pull_source_update accepts 7 parameters: name, sourceId, dedupDays, conditions, scheduleTime, maxLeadsPerRun, intervalMinutes. Required: sourceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on happ_crm_pull_source_update? +

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

happ_crm_pull_source_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit happ_crm_pull_source_update? +

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

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

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

KEEP EXPLORING

More on Platform, and thousands of servers like it.

This server

All 275 Platform tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →