list_accounts

List MTProto account aliases, credential completeness and explicit enablement status without exposing credentials.

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/list-accounts.md

WHAT IT DOES

What list_accounts does on Telegram Bot

AI agents call list_accounts 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 list_accounts is rated Low

Even though list_accounts 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 list_accounts 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 list_accounts, this is the rule to start with:

list_accounts Allowed

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

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 list_accounts call is checked against it from then on.

FAQ

Questions about list_accounts

What does the list_accounts tool do? +

List MTProto account aliases, credential completeness and explicit enablement status without exposing credentials. 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 list_accounts? +

Register the Telegram Bot MCP server in PolicyLayer and add a rule for list_accounts: 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 list_accounts? +

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

Can I rate-limit list_accounts? +

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

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

list_accounts 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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