Login to Telegram via QR code. Returns QR image. IMPORTANT: pass the entire result to user without modifications.
AI agents invoke telegram-login to trigger actions in MCP-Telegram. 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.
This tool initiates an authentication session on Telegram, triggering an external operation (OAuth/QR-based login flow via MTProto). It is not a simple read — it establishes a session with side effects (authenticated session creation). Since it operates as a userbot under a personal Telegram account with full access to chats, contacts, and message history, misuse could grant an attacker full account access.
From the tool's definition Login to Telegram via QR code. Returns QR image.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access telegram-login 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-login:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-login": {
"limits": [
{
"counter": "telegram-login_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} telegram-login 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.
Free to start. No card required.
Login to Telegram via QR code. Returns QR image. IMPORTANT: pass the entire result to user without modifications. It is categorised as a Execute tool in the MCP-Telegram MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-login: 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-login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the telegram-login 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-login. 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-login 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.