widgets_get_embed_code
Get the embed code snippet for a livechat widget. Returns HTML/JavaScript code to add to your website. The code should be placed before the closing </body> tag. Use this when user wants to install the chat widget on their site.
This record as markdown: /tools/io-github-saloprj-dialogbrain/widgets-get-embed-code.md
What widgets_get_embed_code does on Dialogbrain
AI agents call widgets_get_embed_code 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 get embed code for |
Parameters from the server's own tool schema.
Why widgets_get_embed_code is rated Low
This tool retrieves and returns existing embed code for a livechat widget—a configuration artifact that already exists on the server. It performs no writes, modifications, executions, deletions, or financial operations. The returned code is inert HTML/JavaScript meant to be deployed elsewhere; the tool itself does not execute it or cause side effects.
From the tool's definition The tool description explicitly states it 'Get[s] the embed code snippet' and 'Returns HTML/JavaScript code'. The verb 'get' and the action of retrieving code without modification are characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs widgets_get_embed_code 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_embed_code, this is the rule to start with:
widgets_get_embed_code 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_embed_code call is checked against it from then on.
Questions about widgets_get_embed_code
Get the embed code snippet for a livechat widget. Returns HTML/JavaScript code to add to your website. The code should be placed before the closing </body> tag. Use this when user wants to install the chat widget on their site. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
widgets_get_embed_code 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_embed_code: 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_embed_code 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_embed_code 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_embed_code. 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_embed_code 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