calls_list_active
List active voice calls in this workspace. Use before calls.make on a Telegram account (only one MTProto call per account at a time) to check whether the line is free.
This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-list-active.md
What calls_list_active does on Dialogbrain
AI agents call calls_list_active to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
channel | string | — | Filter by voice channel. OMIT to include all channels. |
channel_account_id | integer | — | Filter by channel_account.id (the calling Telegram account or Twilio number). Combine with channel for a per-line busy check. |
Parameters from the server's own tool schema.
Why calls_list_active is rated Low
This tool queries the state of active voice calls without modifying, creating, deleting, or executing any operations. It is a read-only lookup utility to inform decision-making for subsequent actions. The low severity reflects minimal blast radius; misuse would only reveal information about active calls, not cause harm.
From the tool's definition Tool name contains 'list' and description states 'List active voice calls' — a retrieval operation with no modification or side effects. Used for checking state before other operations.
Attacks that exploit this kind of access
The rule that runs calls_list_active 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_list_active, this is the rule to start with:
calls_list_active is read-only, so it stays allowed. 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_list_active call is checked against it from then on.
Questions about calls_list_active
List active voice calls in this workspace. Use before calls.make on a Telegram account (only one MTProto call per account at a time) to check whether the line is free. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
calls_list_active accepts 2 parameters: channel, channel_account_id. 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_list_active: 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_list_active is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the calls_list_active 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_list_active. 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_list_active 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