calls_mute_translation_tts

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

High RISK CLASS

Category Execute

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-mute-translation-tts.md

WHAT IT DOES

What calls_mute_translation_tts does on Dialogbrain

AI agents invoke calls_mute_translation_tts 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
`muted`	boolean	Yes	true to mute, false to unmute.
`scope`	string	—	'call' (default; Google Meet only): silent in the call only — app audio + subtitles keep flowing. 'everywhere' (any channel): no TTS synthesis at all (subtitles
`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.

Parameters from the server's own tool schema.

RISK

Why calls_mute_translation_tts is rated High

This tool triggers an external operation on an active call session — cutting or restoring live audio synthesis in real-time. It does not merely read or write data, but executes a state change on an ongoing live communication channel (Google Meet or other). It's reversible (muted=false reverses it), so not Destructive, but the real-time external effect on active calls places it firmly in Execute.

From the tool's definition Mute or unmute an active call's live-translation TTS... the translator goes silent INSIDE the call — in-flight audio is cut immediately... stop synthesizing entirely from the next utterance

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calls_mute_translation_tts Rate-limited

calls_mute_translation_tts 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_mute_translation_tts": {
      "limits": [
        {
          "counter": "calls_mute_translation_tts_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_mute_translation_tts call is checked against it from then on.

FAQ

Questions about calls_mute_translation_tts

What does the calls_mute_translation_tts tool do? +

Mute or unmute an active call's live-translation TTS. scope='call' (default, Google Meet sessions ONLY): the translator goes silent INSIDE the call — participants hear no bot voice, in-flight audio is cut immediately, but translation audio + subtitles remain available in the app (listen overlay). scope='everywhere' (any channel): stop synthesizing entirely from the next utterance — subtitles only, no audio anywhere. muted=false reverses either. Translation itself keeps running throughout. 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_mute_translation_tts accept? +

calls_mute_translation_tts accepts 3 parameters: muted, scope, call_id. Required: muted, 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_mute_translation_tts? +

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

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

Can I rate-limit calls_mute_translation_tts? +

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

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

calls_mute_translation_tts 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 232 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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