This record as markdown: /tools/creativelead-unclick/telegram-get-updates.md
What telegram_get_updates does on UnClick
AI agents call telegram_get_updates 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 | — | |
timeout | number | — | |
bot_token | string | — |
Parameters from the server's own tool schema.
Why telegram_get_updates is rated Low
This tool retrieves incoming messages or updates for a Telegram bot without modifying, executing, or deleting any data. It is a query operation similar to checking a mailbox—purely informational with no capability to alter state, execute commands, or cause financial/destructive effects.
From the tool's definition Tool name 'telegram_get_updates' and description 'Get Telegram bot updates' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of fetching updates are consistent with the Read category.
Attacks that exploit this kind of access
The rule that runs telegram_get_updates 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_get_updates, this is the rule to start with:
telegram_get_updates 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_get_updates call is checked against it from then on.
Questions about telegram_get_updates
Get Telegram bot updates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
telegram_get_updates accepts 4 parameters: limit, offset, timeout, 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_get_updates: 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_get_updates 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_updates 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_updates. 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_updates 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