Fetch messages from a Telegram chat. Returns message text, sender, date,
AI agents call telegram_get_history 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 historical message data from a Telegram chat without creating, modifying, or deleting any content. It is a read operation. However, severity is elevated to 'medium' rather than 'low' because unauthorized access to chat history could expose sensitive personal communications, authentication tokens, or confidential information shared in private chats—a meaningful privacy and security risk if an AI…
From the tool's definition Tool name 'telegram_get_history' and description 'Fetch messages from a Telegram chat. Returns message text, sender, date' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Fetch messages from a Telegram chat. Returns message text, sender, date,. 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 telegram_get_history: 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.
telegram_get_history 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_history 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_history. 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_history is provided by the Telegram MCP Server MCP server (raidenyn/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →