widgets_get
Get full configuration of a single livechat widget. Returns all settings including theme, identification, actions, and more. Use this when user wants to see or verify a specific widget's settings.
This record as markdown: /tools/io-github-saloprj-dialogbrain/widgets-get.md
What widgets_get does on Dialogbrain
AI agents call widgets_get 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 |
|---|---|---|---|
widget_id | integer | Yes | ID of the widget to retrieve |
Parameters from the server's own tool schema.
Why widgets_get is rated Low
This tool retrieves and returns configuration data for a livechat widget. It performs a read-only query operation with no side effects, no data modification, and no irreversible actions. The description explicitly states it returns settings without indicating any write, delete, or execute capabilities.
From the tool's definition Tool name 'widgets_get' and description 'Get full configuration of a single livechat widget. Returns all settings including theme, identification, actions, and more.' indicate retrieval of widget configuration data with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs widgets_get 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_get, this is the rule to start with:
widgets_get 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_get call is checked against it from then on.
Questions about widgets_get
Get full configuration of a single livechat widget. Returns all settings including theme, identification, actions, and more. Use this when user wants to see or verify a specific widget's settings. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
widgets_get accepts 1 parameter: widget_id. 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_get: 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_get 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_get 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_get. 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_get 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