AI agents call telegram_read to retrieve information from UnClick without modifying anything — 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 | Yes |
Parameters from the server's own tool schema.
This tool retrieves data (Telegram messages and updates) without side effects or the ability to modify, delete, or execute actions. It falls squarely within the Read category. Severity is low because reading messages presents minimal risk compared to tools that could modify data, execute code, or access financial systems. Confidence is high given the clear and explicit naming and description.
From the tool's definition Tool name explicitly states 'read' and description confirms 'Read Telegram messages/updates' with no modification or deletion capabilities indicated.
Attacks that exploit this kind of access
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. Required: 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 (@unclick/mcp-server). 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 →