This record as markdown: /tools/creativelead-unclick/telegram-read.md
What telegram_read does on UnClick
AI agents call telegram_read to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
offset | number | — | |
bot_token | string | — |
Parameters from the server's own tool schema.
Why telegram_read is rated Low
This tool retrieves message data from Telegram without modifying or deleting anything, placing it in the Read category. Severity is rated high because unauthorized access to private messages could expose sensitive personal, financial, or business communications, and an AI agent with this capability could breach user privacy at scale across the 60+ integrated services.
From the tool's definition Tool name is 'telegram_read' and description explicitly states 'Read Telegram messages/updates.' The verb 'read' and absence of any modification language confirm this is a retrieval operation.
Attacks that exploit this kind of access
The rule that runs telegram_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For telegram_read, this is the rule to start with:
telegram_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every telegram_read call is checked against it from then on.
Questions about telegram_read
Read Telegram messages/updates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
telegram_read accepts 3 parameters: limit, offset, bot_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for telegram_read: 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 UnClick. Nothing to install.
telegram_read 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_read 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_read. 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_read is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue