get_account_stats

THE RISK

Low Risk

Why get_account_stats needs a policy

This tool queries and returns account statistics without creating, modifying, deleting, or executing any operations. It is a pure read operation that retrieves existing data about account performance metrics or usage information.

From the tool's definition Tool name 'get_account_stats' and description 'retrieves detailed statistics data for a specified account' indicate data retrieval with no side effects or modifications.

Documented attack patterns abuse exactly the kind of access get_account_stats gives an agent:

POLICY

How to control get_account_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for get_account_stats:

policy.json

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

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

Create a free account and register Telegram MCP Complete — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Telegram MCP Complete tools

Destructive batch_delete_accounts 批量删除多个账号 Destructive delete_account 删除指定的账号（无法删除default账号） Destructive delete_channel 删除频道/群组 Destructive delete_chat_photo 删除群组/频道头像 Destructive delete_contact 删除联系人 Destructive delete_message 删除消息 Destructive delete_proxy 删除指定的代理配置 Destructive delete_schedule 删除定时任务

All 153 Telegram MCP Complete tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_account_stats

What does the get_account_stats tool do? +

获取指定账号的详细统计数据. It is categorised as a Read tool in the Telegram MCP Complete MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_stats? +

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

What risk level is get_account_stats? +

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

Can I rate-limit get_account_stats? +

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

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

get_account_stats is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Telegram MCP Complete tool call.

Start from Telegram MCP Complete, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →