Fetch metadata + an optional initial slice of participants for the active group call (voice/video chat) attached to a chat (phone.GetGroupCall). Returns call info (id, accessHash, participantsCount, title, scheduleDate, recordStartDate, streamDcId, flags) plus a participant slice (peer, date, mut...
AI agents call telegram-get-group-call to retrieve information from MCP-Telegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and participant information from an active group call. While it accesses sensitive information (participant lists, call metadata) within a userbot context with full account access, the operation itself is read-only with no side effects.
From the tool's definition Tool description explicitly states 'Read-only' and 'Fetch metadata' with 'Returns call info' and 'participant slice'. The function retrieves existing group call data without modifying state.
Documented attack patterns abuse exactly the kind of access telegram-get-group-call gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-get-group-call:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-group-call": {}
}
} telegram-get-group-call is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch metadata + an optional initial slice of participants for the active group call (voice/video chat) attached to a chat (phone.GetGroupCall). Returns call info (id, accessHash, participantsCount, title, scheduleDate, recordStartDate, streamDcId, flags) plus a participant slice (peer, date, muted/left/self flags, source, volume, video/presentation indicators) and participantsNextOffset. Pass limit:0 (default) for metadata only. Opt-in: register only when MCP_TELEGRAM_ENABLE_GROUP_CALLS=1. Read-only. It is categorised as a Read tool in the MCP-Telegram MCP Server, which means it retrieves data without modifying state.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-get-group-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 MCP-Telegram. Nothing to install.
telegram-get-group-call 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 telegram-get-group-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.
Set action: deny in the PolicyLayer policy for telegram-get-group-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.
telegram-get-group-call is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.