List who has read a message in a small group (≤100 members, ≤7 days old). Returns readers with userId, readAt timestamp. Does NOT work for channels or groups over 100 members (CHAT_TOO_BIG).
AI agents call telegram-get-message-read-participants to retrieve information from MCP-Telegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves metadata about message read status and reader information. While it is a read operation without direct destructive capability, the severity is elevated to medium because: (1) it operates under a personal Telegram account with full userbot access, (2) it reveals privacy-sensitive information (who read messages and when), and (3) in the context of an AI agent with unrestricted access, this could…
From the tool's definition Tool description explicitly states it "List who has read a message" and "Returns readers with userId, readAt timestamp." This is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access telegram-get-message-read-participants gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-get-message-read-participants:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-message-read-participants": {}
}
}telegram-get-message-read-participants 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.
List who has read a message in a small group (≤100 members, ≤7 days old). Returns readers with userId, readAt timestamp. Does NOT work for channels or groups over 100 members (CHAT_TOO_BIG). It is categorised as a Read tool in the MCP-Telegram MCP Server, which means it retrieves data without modifying state.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-get-message-read-participants: 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 MCP-Telegram. Nothing to install.
telegram-get-message-read-participants 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 telegram-get-message-read-participants 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 telegram-get-message-read-participants. 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.
telegram-get-message-read-participants is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, 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.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.