calls_meet_browser

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-meet-browser.md

WHAT IT DOES

What calls_meet_browser does on Dialogbrain

AI agents invoke calls_meet_browser 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
`call_id`	string	Yes	The meet session's call_id (UUID), e.g. from calls.send_to_meet's session_id or calls.list_active.

Parameters from the server's own tool schema.

RISK

Why calls_meet_browser is rated High

This tool attaches to and controls a live browser session, enabling arbitrary browser actions (click, evaluate JavaScript, inspect network requests) on a running Google Meet bot. This is a classic Execute category: it triggers external operations and runs actions in a live browser whose effects depend on the arguments passed.

From the tool's definition 'Attach to a Google Meet bot's live browser', 'drive the bot's Meet page with the generic browser tools (browser.snapshot / browser.click / browser.take_screenshot / browser.evaluate / browser.console_messages / browser.network_requests)', 'click guest-side…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs calls_meet_browser 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 calls_meet_browser, this is the rule to start with:

calls_meet_browser Rate-limited

calls_meet_browser 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calls_meet_browser": {
      "limits": [
        {
          "counter": "calls_meet_browser_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every calls_meet_browser call is checked against it from then on.

FAQ

Questions about calls_meet_browser

What does the calls_meet_browser tool do? +

Attach to a Google Meet bot's live browser to diagnose and recover a bot that isn't visibly joining. Pass the meet session's call_id; returns a page_id. Then drive the bot's Meet page with the generic browser tools (browser.snapshot / browser.click / browser.take_screenshot / browser.evaluate / browser.console_messages / browser.network_requests) using that page_id — read the snapshot to see whether the bot is in the lobby, blocked, or admitted, and click guest-side controls to recover a stalled join. Note: host admission ('Admit') happens in the host's own browser and is not present on the bot's page. 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.

What parameters does calls_meet_browser accept? +

calls_meet_browser accepts 1 parameter: call_id. Required: call_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calls_meet_browser? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for calls_meet_browser: 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.

What risk level is calls_meet_browser? +

calls_meet_browser is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit calls_meet_browser? +

Yes. Add a rate_limit block to the calls_meet_browser 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.

How do I block calls_meet_browser completely? +

Set action: deny in the PolicyLayer policy for calls_meet_browser. 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.

What MCP server provides calls_meet_browser? +

calls_meet_browser 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.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →