widgets_list
List all livechat widgets. Returns widgets with their configuration, embed code, and status. Use this when user wants to see their widgets or chat widgets.
This record as markdown: /tools/io-github-saloprj-dialogbrain/widgets-list.md
What widgets_list does on Dialogbrain
AI agents call widgets_list to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
active_only | boolean | — | Only return active widgets. OMIT to include inactive widgets too. |
Parameters from the server's own tool schema.
Why widgets_list is rated Low
This tool retrieves and queries widget configuration data without creating, modifying, deleting, executing code, or moving money. It is a standard read operation that simply enumerates existing widgets and their metadata.
From the tool's definition Tool name is 'widgets_list' and description states 'List all livechat widgets' with 'Returns widgets with their configuration, embed code, and status.' The verb 'list' and 'returns' indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs widgets_list 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_list, this is the rule to start with:
widgets_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about widgets_list
List all livechat widgets. Returns widgets with their configuration, embed code, and status. Use this when user wants to see their widgets or chat widgets. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
widgets_list accepts 1 parameter: active_only. 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_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the widgets_list 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_list. 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_list 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