Low Risk

telegram-status

Check Telegram connection status

How to control telegram-status ↓

What telegram-status does on MCP-Telegram

AI agents call telegram-status 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.

Low Risk

Why telegram-status needs a policy

This tool only retrieves status information about the Telegram connection. It performs no modifications, deletions, executions, or financial operations. While the server itself operates as a userbot with broad access to account data, this specific tool is limited to checking connection status, making it a benign Read operation with minimal blast radius if misused.

From the tool's definition The tool name is 'telegram-status' and description states it 'Check[s] Telegram connection status' — a read-only query operation that retrieves connection state information with no side effects.

Documented attack patterns abuse exactly the kind of access telegram-status gives an agent:

How to control telegram-status

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-status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram-status": {}
  }
}

telegram-status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-Telegram — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about telegram-status

What does the telegram-status tool do? +

Check Telegram connection status. It is categorised as a Read tool in the MCP-Telegram MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on telegram-status? +

Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-status: 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.

What risk level is telegram-status? +

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

Can I rate-limit telegram-status? +

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

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

telegram-status 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.

Enforce policy on every MCP-Telegram tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.