present_tab
Share the agent's browser tab on the live call so everyone sees it as a real screen-share. Pass the page_id you got from browser.open. Only usable while the agent is in an active voice call. The shared tab stays the active share until you call present_tab with a different page_id, close the tab v...
This record as markdown: /tools/io-github-saloprj-dialogbrain/present-tab.md
What present_tab does on Dialogbrain
AI agents invoke present_tab to trigger actions in Dialogbrain. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
page_id | string | Yes | page_id returned by browser.open for the tab you want to share. Must be a tab still open in the agent's browser context. |
Parameters from the server's own tool schema.
Why present_tab is rated High
This tool triggers an external operation (screen-sharing a browser tab to live call participants) that has real-time effects on an ongoing voice call. It doesn't just read or write data — it actively changes what all call participants see, making it an Execute-category action. Misuse could expose sensitive browser content to unintended audiences during a live call.
From the tool's definition Share the agent's browser tab on the live call so everyone sees it as a real screen-share... Only usable while the agent is in an active voice call.
Attacks that exploit this kind of access
The rule that runs present_tab 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 present_tab, this is the rule to start with:
present_tab stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 present_tab call is checked against it from then on.
Questions about present_tab
Share the agent's browser tab on the live call so everyone sees it as a real screen-share. Pass the page_id you got from browser.open. Only usable while the agent is in an active voice call. The shared tab stays the active share until you call present_tab with a different page_id, close the tab via browser.close, or the call ends. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
present_tab accepts 1 parameter: page_id. Required: page_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 present_tab: 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.
present_tab is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the present_tab 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 present_tab. 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.
present_tab 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