This record as markdown: /tools/creativelead-unclick/telegram-search.md
What telegram_search does on UnClick
AI agents call telegram_search 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 |
|---|---|---|---|
query | string | — | |
chat_id | string | — | |
bot_token | string | — |
Parameters from the server's own tool schema.
Why telegram_search is rated Low
This tool retrieves and queries message data from Telegram chats without creating, modifying, deleting, or executing any external operations. Search operations are non-destructive reads. Severity is low because while it accesses communications data, the blast radius of an agent misusing a search function is limited to information disclosure rather than system-wide impact.
From the tool's definition Tool performs a search operation on Telegram messages ('Search Telegram messages in a chat'). The verb 'search' indicates retrieval/querying of existing data without modification or deletion.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs telegram_search 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_search, this is the rule to start with:
telegram_search 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_search call is checked against it from then on.
Questions about telegram_search
Search Telegram messages in a chat. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
telegram_search accepts 3 parameters: query, chat_id, 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_search: 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_search 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_search 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_search. 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_search 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