refresh_stats

Force recalculation of global telegram-archive statistics

Part of the Telegram Archive MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents call refresh_stats to retrieve information from Telegram Archive without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON REFRESH_STATS

Even though refresh_stats only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-geiserx-telegram-archive-mcp.yaml

tools:
  refresh_stats:
    rules:
      - action: allow

See the full Telegram Archive policy for all 7 tools.

// DETAILS

Tool Name refresh_stats

Category Read

MCP Server Telegram Archive MCP Server

Risk Level Low

// MORE TELEGRAM ARCHIVE TOOLS

Read get_chat_stats Read get_messages Read get_messages_by_date Read get_pinned_messages Read get_topics Read search_messages

// WHAT CAN GO WRONG

Agents calling read-class tools like refresh_stats have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the refresh_stats tool do? +

Force recalculation of global telegram-archive statistics. It is categorised as a Read tool in the Telegram Archive MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on refresh_stats? +

Add a rule in your Intercept YAML policy under the tools section for refresh_stats. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Telegram Archive MCP server.

What risk level is refresh_stats? +

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

Can I rate-limit refresh_stats? +

Yes. Add a rate_limit block to the refresh_stats rule in your Intercept 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 refresh_stats completely? +

Set action: deny in the Intercept policy for refresh_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 refresh_stats? +

refresh_stats is provided by the Telegram Archive MCP server (telegram-archive-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

refresh_stats

Enforce policies on Telegram Archive