widgets_delete
Delete a livechat widget permanently. This will remove the widget and its embed code will stop working. Existing chat history will be preserved. Use this when user wants to remove a chat widget.
This record as markdown: /tools/io-github-saloprj-dialogbrain/widgets-delete.md
What widgets_delete does on Dialogbrain
AI agents call widgets_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
widget_id | integer | Yes | ID of the widget to delete |
Parameters from the server's own tool schema.
Why widgets_delete is rated Critical
This tool permanently deletes a livechat widget configuration, which cannot be undone. While the chat history is preserved, the widget itself and its embed code are irreversibly removed. This is a destructive action with potentially significant operational impact (users lose access to the chat functionality), making it more severe than Write operations.
From the tool's definition Tool description states 'Delete a livechat widget permanently' and 'This will remove the widget and its embed code will stop working.' The words 'delete permanently' and 'remove' indicate irreversible deletion of a configured resource.
Attacks that exploit this kind of access
The rule that runs widgets_delete 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_delete, this is the rule to start with:
widgets_delete 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 Dialogbrain, apply this rule, and every widgets_delete call is checked against it from then on.
Questions about widgets_delete
Delete a livechat widget permanently. This will remove the widget and its embed code will stop working. Existing chat history will be preserved. Use this when user wants to remove a chat widget. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
widgets_delete 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_delete: 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_delete 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 widgets_delete 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_delete. 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_delete 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.
Across the catalogue