calls_send_to_meet
Dispatch a workspace AI agent into an active Google Meet call. The agent joins as a participant — it can hear the conversation, respond via TTS, see the shared screen (when vision is enabled on the agent), and answer questions about what's on screen. Use when the operator wants to delegate live m...
This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-send-to-meet.md
What calls_send_to_meet does on Dialogbrain
AI agents use calls_send_to_meet to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
silent | boolean | — | Silent translator dispatch — the translator NEVER speaks into the Meet call (participants hear no bot voice); translation audio + subtitles stay available insid |
agent_id | integer | Yes | ID of an active agent in this workspace. Get it from agents.list. Any active agent can be dispatched — a voice trigger is NOT required (the runner attaches the |
meet_url | string | Yes | Canonical Google Meet URL — must match https://meet.google.com/<3 letters>-<4 letters>-<3 letters>, e.g. https://meet.google.com/abc-defg-hij. lookup/ redirects |
vision_mode | string | — | Screen-share capture mode. 'off' = no vision (default), 'on_demand' = the agent can call the vision_query tool for fine-detail reads, 'continuous_0_3fps' = the |
instructions | string | — | What the agent should do once it joins — its task brief, e.g. 'greet everyone and present the overview deck' or 'take notes and answer questions about the roadm |
app_languages | array | — | Extra target languages translated for the APP ONLY (shown as subtitles + listenable audio in the inbox), never spoken into the Meet call. Operators switch betwe |
comeback_phrase | string | — | Optional phrase to trigger return to original language during translation (e.g. 'Back to English'). Only used with translation_mode=true. |
target_language | string | — | PRIMARY target language spoken INTO the Meet call when translation_mode=true (e.g. 'en', 'es', 'fr'). OMIT to not use translation. |
translation_mode | boolean | — | If true, pre-arm translator mode (auto-target language) on join with zero verbal trigger. Forces the original-speaker audio track to exist. Requires target_lang |
start_immediately | boolean | — | If true, the agent starts talking as soon as it joins — it greets everyone and begins the task in `instructions` without waiting for someone to say a wake-word. |
Parameters from the server's own tool schema.
Why calls_send_to_meet is rated Medium
An AI agent can call calls_send_to_meet faster than any human can review: one bad instruction and it creates or modifies resources in Dialogbrain by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs calls_send_to_meet 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_send_to_meet, this is the rule to start with:
calls_send_to_meet stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 calls_send_to_meet call is checked against it from then on.
Questions about calls_send_to_meet
Dispatch a workspace AI agent into an active Google Meet call. The agent joins as a participant — it can hear the conversation, respond via TTS, see the shared screen (when vision is enabled on the agent), and answer questions about what's on screen. Use when the operator wants to delegate live meeting attendance to an agent (notes, Q&A, summarization, real-time support). The Meet URL must be in canonical 3-4-3 form, e.g. https://meet.google.com/abc-defg-hij. Lookup-redirect URLs are not supported — operator must use the share-link form. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
calls_send_to_meet accepts 10 parameters: silent, agent_id, meet_url, vision_mode, instructions, app_languages, comeback_phrase, target_language, translation_mode, start_immediately. Required: agent_id, meet_url. 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 calls_send_to_meet: 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.
calls_send_to_meet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calls_send_to_meet 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 calls_send_to_meet. 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.
calls_send_to_meet 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