// SCAN REPORT

Telegram Bot

51 tools. 31 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 22 Oct 2026

31 can modify or destroy data

20 read-only

51 tools total

Community server · catalogue entry checked 22/10/2026

How to control Telegram Bot ↓

TOOL MAP

What Telegram Bot exposes to your agents

Read (20) Write / Execute (29) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Telegram Bot tools

Destructive · High business Use Telegram Business connections, business messages, read/delete actions, stories, gifts and other official Business Bot API methods. Destructive · High message_action Edit, delete, forward, copy, react to, pin, unpin or otherwise manage Telegram messages through an official Bot API method. Write · Medium manage_bot_profile Read or change bot name, about, description, commands, menu button, profile photo and default administrator rights using official Bot API me Write · Medium call_bot_api Call official Telegram Bot API methods except credential export/rotation. Server-side attachment downloads are disabled. Use this forward-co

31 of Telegram Bot's 51 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Telegram Bot

PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram Bot, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "business": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "call_bot_api": {
    "limits": [
      {
        "counter": "call_bot_api_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "answer_inbox_callback": {
    "limits": [
      {
        "counter": "answer_inbox_callback_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Telegram Bot — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TELEGRAM BOT →

Instant setup, no code required.

FULL CATALOGUE

All 51 Telegram Bot tools

DESTRUCTIVE 2 tools

Destructive business Use Telegram Business connections, business messages, read/delete actions, stories, gifts and other official B Destructive message_action Edit, delete, forward, copy, react to, pin, unpin or otherwise manage Telegram messages through an official Bo

WRITE 29 tools

Write call_bot_api Call official Telegram Bot API methods except credential export/rotation. Server-side attachment downloads are Write chat_admin Manage groups, supergroups, channels, forum topics, members, admins, permissions, bans, invites, join requests Write compose_daily_report Read-only deterministic draft for new-user next-day retention, active next-day retention, chat rate, mode mess Write connect_bot_inbox Explicit registration only after approval of Bot, destinations and retention. Requires separately configured r Write connect_default_inbox Requires user approval of retention and destination. Registers only the configured cloud receiver, only if no Write create_managed_bot Unavailable in this conservative candidate. Creating Managed Bots requires a separately approved secure manage Write dispatch_report_chunk Separately default-denied sending workflow. Sends at most one queued chunk to the exact approved destination. Write draft_payment_order Default-disabled owner order storage. Requires approved Bot/payer scope. Same ID is immutable and idempotent. Write draft_report Default-disabled owner workflow. Persist an authorized report with immutable content/destination fingerprint a Write edit_managed_bot Unavailable in this conservative candidate. Editing owned bots requires a separately scoped management workflo Write edit_rich_message Replace the whole Rich Message for an explicit message ID; use a fresh key for new content. Same-key retry ret Write enqueue_report Default-disabled. Enqueue the exact stored fingerprint; this does not send. A hash alone is not user consent. Write manage_bot_avatar Inspect, replace with explicit JPEG/MPEG4 bytes, or remove the selected bot avatar. Writes require reviewed bo Write manage_bot_profile Read or change bot name, about, description, commands, menu button, profile photo and default administrator ri Write manage_webhook Set, delete or inspect a bot webhook and its allowed update types. Write managed_bot_access Read or update access restrictions for a Telegram Managed Bot using its manager bot. Write managed_bot_token Managed Bot token operations are unavailable through chat until a secure credential handoff/storage flow is im Write payments Use Telegram invoices, Stars balances and transactions, refunds, subscriptions, paid media, gifts and other of Write plan_report Prepare a deterministic plain-text report split into bounded Unicode-safe messages. Read-only: no Telegram req Write recover_report Default-disabled owner workflow. Marks expired in-flight claims unknown; does not resend or assume non-deliver Write rich_stream Create, preview, finalize, stop or inspect a persistent rich session. Full snapshots only; revision required. Write send_account_message Send a Telegram message using an authorized personal MTProto account. Write send_callback_message Default-disabled. Requires explicit user approval of text, button labels/data and configured destination. Chec Write send_file_once Default-disabled single file upload, up to 2 MiB. Requires explicit approval of bytes and destination, matchin Write send_media Send photos, videos, audio, voice, animation, documents, video notes, stickers, locations, contacts, polls, di Write send_media_bytes Default-disabled: upload explicitly supplied base64 files with an approved bot and exact chat scope. No URL do Write send_message Send a text message using a selected bot to a chat alias or Telegram chat ID. Defaults preserve the Telegram d Write send_message_draft Explicitly approved private-chat preview only, default disabled. Acknowledgement is not persisted delivery. Re Write send_rich_message Explicitly authorized Rich Message to default/demo-group only. Durable idempotency; no automatic retry or fall

READ 20 tools

Read answer_inbox_callback Default-disabled. Requires explicit user approval of answering the selected inbox sequence and text. Resolves Read call_mtproto Read-only allowlist: messages.getHistory (peer, limit?, offsetId?), messages.search (peer, q, limit?, offsetId Read check_managed_bot_username Check whether a Telegram username can be used for a new Managed Bot. Read check_rich_message Validate phase-one structured blocks and supplied image hashes without sending. Not native rendering. Read get_account_me Get the identity of a configured authorized MTProto personal account. Read get_file_send_status Read the durable receipt for the exact bot and caller idempotency key. No file bytes, new claim, network send Read get_payment_order_status Default-disabled owner-scoped order summary. Does not return payer identity, invoice payload or charge IDs. Ob Read get_report_status Default-disabled owner workflow. Read report state/receipts without returning report text. Read get_rich_message_status Read durable receipt only; never resend unknown outcomes. Read inspect_bot_inbox Read a specified configured Bot webhook status without exposing URL, secret or provider error text. Does not r Read inspect_business_connection Read one explicitly selected Business connection and its granted rights. Requires an existing bot alias and co Read inspect_configuration Read-only counts, configuration validation and explicit feature switches. Never exposes credentials, aliases o Read inspect_default_inbox Read-only setup check. Returns whether a webhook exists and pending update count, without exposing its URL or Read list_accounts List MTProto account aliases, credential completeness and explicit enablement status without exposing credenti Read list_bots List configured Telegram bot aliases without exposing tokens. Read list_chats List configured Telegram chat aliases and IDs. Read list_dialogs List private chats, groups and channels visible to a configured Telegram personal account. Read read_business_notices Default-disabled owner-only notification journal. Read one explicitly configured Bot and Business connection; Read read_inbox Default-disabled owner workflow. Reads only configured bot/chat/Business scope, hides expired events and respe Read search_account_messages Search message history inside a chat visible to an authorized Telegram personal account.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Telegram Bot

Can an AI agent delete data through the Telegram Bot MCP server? +

Yes. The Telegram Bot server exposes 2 destructive tools including business, message_action. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Telegram Bot? +

The Telegram Bot server has 29 write tools including call_bot_api, chat_admin, compose_daily_report. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Telegram Bot.

How many tools does the Telegram Bot MCP server expose? +

51 tools across 3 categories: Destructive, Read, Write. 20 are read-only. 31 can modify, create, or delete data.

How do I enforce a policy on Telegram Bot? +

Register the Telegram Bot MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Telegram Bot tool call.

Deterministic rules across all 51 Telegram Bot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TELEGRAM BOT →

Instant setup, no code required.

51 Telegram Bot tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Telegram Bot's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →