happ_telegram_push_destinations
Чаты, куда компания может слать уведомления (личка + группы, куда добавлен бот), и текущая маршрутизация по видам событий . Группа появляется здесь после того, как бота добавили в неё. (GET /telegram-push-notifications/:companyId/destinations)
This record as markdown: /tools/happ-ai-platform-mcp/happ-telegram-push-destinations.md
What happ_telegram_push_destinations does on Platform
AI agents use happ_telegram_push_destinations 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 |
|---|---|---|---|
companyId | string | Yes | ID компании |
Parameters from the server's own tool schema.
Why happ_telegram_push_destinations is rated Medium
An AI agent can call happ_telegram_push_destinations 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_telegram_push_destinations 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_telegram_push_destinations, this is the rule to start with:
happ_telegram_push_destinations 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_telegram_push_destinations call is checked against it from then on.
Questions about happ_telegram_push_destinations
Чаты, куда компания может слать уведомления (личка + группы, куда добавлен бот), и текущая маршрутизация по видам событий . Группа появляется здесь после того, как бота добавили в неё. (GET /telegram-push-notifications/:companyId/destinations). 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_telegram_push_destinations accepts 1 parameter: companyId. Required: 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_telegram_push_destinations: 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_telegram_push_destinations 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_telegram_push_destinations 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_telegram_push_destinations. 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_telegram_push_destinations 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