Returns summary statistics for stored messages in a channel.
AI agents call getSyncedMessageStats to retrieve information from Telegram MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about messages in a channel—a read-only query operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal; an AI agent could only over-query or leak metadata about message counts/statistics, which poses low risk compared to other categories.
From the tool's definition Tool name 'getSyncedMessageStats' and description 'Returns summary statistics for stored messages in a channel' indicate a retrieval operation that queries and returns aggregated data without modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access getSyncedMessageStats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getSyncedMessageStats:
{
"version": "1",
"default": "deny",
"tools": {
"getSyncedMessageStats": {}
}
} getSyncedMessageStats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns summary statistics for stored messages in a channel. It is categorised as a Read tool in the Telegram MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Server MCP server in PolicyLayer and add a rule for getSyncedMessageStats: 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 Server. Nothing to install.
getSyncedMessageStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getSyncedMessageStats 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.
Set action: deny in the PolicyLayer policy for getSyncedMessageStats. 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.
getSyncedMessageStats is provided by the Telegram MCP Server MCP server (kfastov/tgcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Server, 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.
38 Telegram MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.