widgets_update
Update an existing livechat widget configuration. You can change name, theme, auto-reply mode, and other settings. Only provided fields will be updated. Use this when user wants to modify their chat widget settings.
This record as markdown: /tools/io-github-saloprj-dialogbrain/widgets-update.md
What widgets_update does on Dialogbrain
AI agents use widgets_update to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New name for the widget |
position | string | — | Widget position on screen. OMIT to leave the position unchanged. |
is_active | boolean | — | Enable or disable the widget. OMIT to leave the active flag unchanged. |
widget_id | integer | Yes | ID of the widget to update |
allow_voice | boolean | — | Master switch for voice on this widget — set true to show the mic and let visitors talk to the agent. Everything else voice-related (greeting, button label, STT |
website_url | string | — | Website URL for product/site search integration |
calendly_url | string | — | Booking URL for calendar action (e.g., 'https://calendly.com/yourname') |
color_scheme | string | — | Widget color scheme. 'auto' follows the visitor's OS dark/light mode preference. OMIT to leave the color scheme unchanged. |
display_mode | string | — | Visual mode of the widget. Pick exactly one: - 'chat': full chat panel + voice mic — default for support / sales / general. - 'voice_only': mic-only bubble that |
header_title | string | — | Title shown in chat header |
greeting_text | string | — | Custom greeting message shown when visitor opens the chat (e.g., 'Hello! How can I help you today?') |
primary_color | string | — | Primary color for widget theme (hex, e.g., '#2563eb') |
Parameters from the server's own tool schema.
Why widgets_update is rated Medium
This tool modifies widget configuration settings (name, theme, auto-reply mode) but does not delete data or execute arbitrary code. The changes are reversible through subsequent updates. While it could affect customer-facing chat behavior if misconfigured, the impact is limited to widget settings within the Dialogbrain system.
From the tool's definition Tool description explicitly states "Update an existing livechat widget configuration" and "change name, theme, auto-reply mode, and other settings." The verb "update" and focus on modifying configuration settings indicate reversible data modification.
Risk signalsHigh parameter count (29 properties)
Attacks that exploit this kind of access
The rule that runs widgets_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For widgets_update, this is the rule to start with:
widgets_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every widgets_update call is checked against it from then on.
Questions about widgets_update
Update an existing livechat widget configuration. You can change name, theme, auto-reply mode, and other settings. Only provided fields will be updated. Use this when user wants to modify their chat widget settings. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
widgets_update accepts 12 parameters: name, position, is_active, widget_id, allow_voice, website_url, calendly_url, color_scheme, display_mode, header_title, greeting_text, primary_color. Required: widget_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for widgets_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 Dialogbrain. Nothing to install.
widgets_update 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 widgets_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.
Set action: deny in the PolicyLayer policy for widgets_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.
widgets_update is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue