happ_notification_channel_mute
Выключает (mute=true) или включает (mute=false) уведомления о новых сообщениях из конкретного канала/интеграции для текущего пользователя. (POST|DELETE /notification-preferences/channels/:companyIntegrationId/mute)
This record as markdown: /tools/happ-ai-platform-mcp/happ-notification-channel-mute.md
What happ_notification_channel_mute does on Platform
AI agents call happ_notification_channel_mute to permanently remove resources in Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
mute | boolean | Yes | true — заглушить, false — включить обратно |
companyId | string | Yes | |
companyIntegrationId | string | Yes | ID интеграции из happ_integrations_list |
Parameters from the server's own tool schema.
Why happ_notification_channel_mute is rated Critical
An AI agent that decides to call happ_notification_channel_mute doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Platform is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs happ_notification_channel_mute 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_notification_channel_mute, this is the rule to start with:
happ_notification_channel_mute is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_notification_channel_mute call is checked against it from then on.
Questions about happ_notification_channel_mute
Выключает (mute=true) или включает (mute=false) уведомления о новых сообщениях из конкретного канала/интеграции для текущего пользователя. (POST|DELETE /notification-preferences/channels/:companyIntegrationId/mute). It is categorised as a Destructive tool in the Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
happ_notification_channel_mute accepts 3 parameters: mute, companyId, companyIntegrationId. Required: mute, companyId, companyIntegrationId. 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_notification_channel_mute: 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_notification_channel_mute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the happ_notification_channel_mute 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_notification_channel_mute. 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_notification_channel_mute 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.
Across the catalogue