telegram_manage_chat
Manage a Telegram chat (get info, ban, kick, etc.).
This record as markdown: /tools/creativelead-unclick/telegram-manage-chat.md
What telegram_manage_chat does on UnClick
AI agents call telegram_manage_chat to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | |
chat_id | string | — | |
user_id | number | — | |
bot_token | string | — |
Parameters from the server's own tool schema.
Why telegram_manage_chat is rated Critical
The tool description explicitly lists 'ban' and 'kick' as operations, which are destructive moderation actions. Banning a user from a Telegram chat can be permanent and irreversible. While 'get info' is a Read operation, the most severe applicable category given the presence of ban/kick functionality is Destructive. Misuse by an AI agent could result in users being permanently removed from chats.
From the tool's definition 'ban, kick' — these are irreversible or difficult-to-reverse moderation actions that remove users from chats
Attacks that exploit this kind of access
The rule that runs telegram_manage_chat 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_manage_chat, this is the rule to start with:
telegram_manage_chat is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every telegram_manage_chat call is checked against it from then on.
Questions about telegram_manage_chat
Manage a Telegram chat (get info, ban, kick, etc.). It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
telegram_manage_chat accepts 4 parameters: action, chat_id, user_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_manage_chat: 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_manage_chat is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the telegram_manage_chat 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_manage_chat. 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_manage_chat 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.
Across the catalogue