calls_set_translation_languages

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

Medium RISK CLASS

Category Write

Parameters 22 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-set-translation-languages.md

WHAT IT DOES

What calls_set_translation_languages does on Dialogbrain

AI agents use calls_set_translation_languages 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
`call_id`	string	Yes	The active call / Meet session call_id (UUID) — e.g. from calls.send_to_meet's session_id or calls.list_active.
`app_languages`	array	Yes	Extra app-only target languages (ISO codes), e.g. ['de','fr','es']. Pass [] to remove all extras. Max 4.

Parameters from the server's own tool schema.

RISK

Why calls_set_translation_languages is rated Medium

This tool creates or modifies call translation preferences within an active call session. It changes configuration state (which languages are translated) but is reversible and has no destructive consequences. The blast radius is medium because misconfiguration could cause communication issues or expose unintended translations, but it does not delete data, execute arbitrary code, or commit financial transactions.

From the tool's definition Tool description states it 'Set[s] the EXTRA target languages' and 'Pass call_id and `app_languages`' — this modifies call translation configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calls_set_translation_languages Rate-limited

calls_set_translation_languages 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_set_translation_languages": {
      "limits": [
        {
          "counter": "calls_set_translation_languages_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_set_translation_languages call is checked against it from then on.

FAQ

Questions about calls_set_translation_languages

What does the calls_set_translation_languages tool do? +

Set the EXTRA target languages an active voice/Meet call's translator produces for the APP ONLY (subtitles + listenable audio in the inbox — NOT spoken into the call). Operators switch between them in the UI. Pass call_id and app_languages (ISO codes, e.g. ['de','fr']); pass [] to drop all extras. Max 4. The primary spoken language is managed by calls.set_translation_language. Takes effect within ~10ms; new languages translate NEW speech 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_set_translation_languages accept? +

calls_set_translation_languages accepts 2 parameters: call_id, app_languages. Required: call_id, app_languages. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calls_set_translation_languages? +

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

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

Can I rate-limit calls_set_translation_languages? +

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

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

calls_set_translation_languages 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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