happ_widget_update

Обновляет настройки веб-виджета: название, описание, список доменов (заменяется целиком). Возвращает актуальный код для вставки. (PATCH /widget/:id)

SERVERPlatform SOURCE@happ-ai/platform-mcp

Medium RISK CLASS

Category Write

Parameters 41 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-widget-update.md

WHAT IT DOES

What happ_widget_update does on Platform

AI agents use happ_widget_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	—
`widgetId`	string	Yes	ID интеграции виджета (companyIntegrationId из happ_integrations_list, НЕ wgt_…)
`description`	string	—
`allowedOrigins`	array	—	Полный новый список доменов без протокола; ['*'] = везде

Parameters from the server's own tool schema.

RISK

Why happ_widget_update is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

happ_widget_update Rate-limited

happ_widget_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_widget_update": {
      "limits": [
        {
          "counter": "happ_widget_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_widget_update call is checked against it from then on.

FAQ

Questions about happ_widget_update

What does the happ_widget_update tool do? +

Обновляет настройки веб-виджета: название, описание, список доменов (заменяется целиком). Возвращает актуальный код для вставки. (PATCH /widget/: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_widget_update accept? +

happ_widget_update accepts 4 parameters: name, widgetId, description, allowedOrigins. Required: widgetId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on happ_widget_update? +

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

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

Can I rate-limit happ_widget_update? +

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

Set action: deny in the PolicyLayer policy for happ_widget_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_widget_update? +

happ_widget_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 →