calls_send_to_telegram_call

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

High RISK CLASS

Category Execute

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-send-to-telegram-call.md

WHAT IT DOES

What calls_send_to_telegram_call does on Dialogbrain

AI agents invoke calls_send_to_telegram_call 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
`target`	string	—	Telegram call or group to join. Either: (1) encrypted group-call slug (https://t.me/call/<slug> URL or bare slug token, 12-64 chars), (2) group reference (@user
`chat_id`	integer	—	Telegram group chat id to join the voice chat of (e.g. -1001234567890 for a supergroup, -4766727451 for a basic group). Use this to target a PRIVATE group that
`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
`vision_mode`	string	—	Screen-share capture mode. 'off' = no vision (default), 'on_demand' = the agent can call vision_query for fine-detail reads, 'continuous_0_3fps' = the bot captu
`instructions`	string	—	What the agent should do once it joins — its task brief, woven into the voice system prompt. e.g. 'present the overview deck' or 'greet everyone and summarize t
`start_if_none`	boolean	—	When joining a group voice chat (not a slug-based encrypted call), spawn a new voice chat if none is active. Default false. Ignored when target is a call slug (
`channel_account_id`	integer	—	Workspace Telegram channel account ID that joins as the bot. Optional — when the workspace has exactly one Telegram account, it's used by default. Required when

Parameters from the server's own tool schema.

RISK

Why calls_send_to_telegram_call is rated High

This tool triggers an external operation — dispatching an AI agent to join and participate in a live voice call on Telegram. It causes real-world side effects (agent joins calls, speaks via TTS, interacts in live sessions) that depend on the arguments provided. It is not merely writing data but executing an active agent operation in a live communication channel, making Execute the appropriate category.

From the tool's definition Dispatch a workspace AI agent into a live Telegram GROUP voice chat OR an encrypted call-link conference... The agent joins via the workspace's Telegram account — hears the call, replies via TTS

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calls_send_to_telegram_call Rate-limited

calls_send_to_telegram_call 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_send_to_telegram_call": {
      "limits": [
        {
          "counter": "calls_send_to_telegram_call_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_send_to_telegram_call call is checked against it from then on.

FAQ

Questions about calls_send_to_telegram_call

What does the calls_send_to_telegram_call tool do? +

Dispatch a workspace AI agent into a live Telegram GROUP voice chat OR an encrypted call-link conference. FOUR ways to target the call: (1) chat_id — the group's numeric id, e.g. -1001234567890 (use for a private group with no @username); (2) target=@username or a t.me/<group> link; (3) omit both target and chat_id to use the CURRENT thread (when it's a Telegram group); (4) target=t.me/call/<slug> encrypted group-call link. start_if_none=true spawns a new voice chat if the group has none active. The agent joins via the workspace's Telegram account — hears the call, replies via TTS, and sees shared screens (when vision is enabled). NOTE: joining a regular in-group voice chat does NOT need a slug link — pass chat_id directly. 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_send_to_telegram_call accept? +

calls_send_to_telegram_call accepts 7 parameters: target, chat_id, agent_id, vision_mode, instructions, start_if_none, channel_account_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calls_send_to_telegram_call? +

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

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

Can I rate-limit calls_send_to_telegram_call? +

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

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

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

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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