call_mtproto

SERVERTelegram Bot SOURCE@cyuanxv/telegram-bot-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cyuanxv-telegram-bot-mcp-server/call-mtproto.md

WHAT IT DOES

What call_mtproto does on Telegram Bot

AI agents call call_mtproto to retrieve information from Telegram Bot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why call_mtproto is rated Low

Even though call_mtproto only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_mtproto safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Telegram Bot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_mtproto, this is the rule to start with:

call_mtproto Allowed

call_mtproto is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_mtproto": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Telegram Bot, apply this rule, and every call_mtproto call is checked against it from then on.

FAQ

Questions about call_mtproto

What does the call_mtproto tool do? +

Read-only allowlist: messages.getHistory (peer, limit?, offsetId?), messages.search (peer, q, limit?, offsetId?), bots.checkUsername (username). peer is a primitive username/me/self/decimal ID. Unknown fields, TL objects, nested requests, authentication and credential methods are rejected. Returns fixed safe fields only; requires explicit MTProto enablement and secure API/session configuration. It is categorised as a Read tool in the Telegram Bot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on call_mtproto? +

Register the Telegram Bot MCP server in PolicyLayer and add a rule for call_mtproto: 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 Telegram Bot. Nothing to install.

What risk level is call_mtproto? +

call_mtproto is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit call_mtproto? +

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

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

call_mtproto is provided by the Telegram Bot MCP server (@cyuanxv/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Telegram Bot, and thousands of servers like it.

This server

All 51 Telegram Bot tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →