telegram_account

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/telegram-account.md

WHAT IT DOES

What telegram_account does on Hermoso

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

RISK

Why telegram_account is rated Low

Even though telegram_account 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 telegram_account safely

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

telegram_account Allowed

telegram_account 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": {
    "telegram_account": {}
  }
}

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

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

FAQ

Questions about telegram_account

What does the telegram_account tool do? +

ACCOUNT-LEVEL numbers for a Telegram channel, group or chat \u2014 its SUBSCRIBER / MEMBER COUNT \u2014 plus title, @username, description, invite link and linked discussion group. This is the answer to \u201chow many subscribers does our Telegram channel have\u201d. WHICH CHAT IS ALWAYS ASKED FOR: pass chatId (a public channel\u2019s @username, or the numeric id) \u2014 the Bot API publishes no method that lists the chats a bot is in, so there is no default and guessing would report another channel\u2019s numbers as this one\u2019s; list_telegram_chats reports any chat that messaged the bot in the last 24 hours. Warning: TELEGRAM HAS NO PER-POST ANALYTICS AT ANY PERMISSION LEVEL: its Message object carries no. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on telegram_account? +

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

What risk level is telegram_account? +

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

Can I rate-limit telegram_account? +

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

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

telegram_account is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

The MCP Attack Database →

Guides

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