calls_dispatch_translator

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

Medium RISK CLASS

Category Write

Parameters 71 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-dispatch-translator.md

WHAT IT DOES

What calls_dispatch_translator does on Dialogbrain

AI agents use calls_dispatch_translator 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
`title`	string	—	native_new only: meeting title.
`silent`	boolean	—	Google Meet only: true = subtitles without speaking into the call. OMIT for a normal speaking translator.
`target`	string	—	Where to send the translator: a meet.google.com link, a Telegram @group / t.me link / chat_id, 'new' for a fresh native meeting, or an existing native meeting c
`app_languages`	array	—	Extra subtitle-only languages (max 4).
`comeback_phrase`	string	—	Attention-recall phrase.
`sentence_length`	string	—	Native meetings only: short\|medium\|long buffering (default medium).
`target_language`	string	Yes	Primary spoken translation target (ISO code, e.g. 'th').

Parameters from the server's own tool schema.

RISK

Why calls_dispatch_translator is rated Medium

An AI agent can call calls_dispatch_translator 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calls_dispatch_translator Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calls_dispatch_translator": {
      "limits": [
        {
          "counter": "calls_dispatch_translator_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_dispatch_translator call is checked against it from then on.

FAQ

Questions about calls_dispatch_translator

What does the calls_dispatch_translator tool do? +

Send a live speech translator to a call. target decides where: a meet.google.com link → Google Meet bot; a Telegram @group / t.me link / chat_id → Telegram group voice chat; 'new' (or omitted) → creates a native DialogBrain meeting with translation on and returns the join + guest links; a native meeting call_id or /meeting/ URL → enables translation on that running meeting. Always pass target_language (ISO code); optional app_languages (extra subtitle-only languages), sentence_length (short|medium|long, native only), silent (subtitles without voice, Google Meet only). 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.

What parameters does calls_dispatch_translator accept? +

calls_dispatch_translator accepts 7 parameters: title, silent, target, app_languages, comeback_phrase, sentence_length, target_language. Required: target_language. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calls_dispatch_translator? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for calls_dispatch_translator: 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_dispatch_translator? +

calls_dispatch_translator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calls_dispatch_translator? +

Yes. Add a rate_limit block to the calls_dispatch_translator 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_dispatch_translator completely? +

Set action: deny in the PolicyLayer policy for calls_dispatch_translator. 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_dispatch_translator? +

calls_dispatch_translator 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →