telegram_manage_chat · UnClick MCP: Risk & Policy

WHAT IT DOES

What telegram_manage_chat does on UnClick

AI agents invoke telegram_manage_chat to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

PARAMETERS

Parameter	Type	Required
`action`	string	Yes
`chat_id`	string	Yes
`user_id`	number	—
`bot_token`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why telegram_manage_chat needs a policy

The tool performs a range of actions on Telegram chats including banning and kicking users, which are privileged moderation operations with significant social consequences. While 'get info' is a read operation, the most severe applicable category is Execute (or potentially Destructive for bans/kicks that may be irreversible depending on context).

From the tool's definition 'ban, kick' — these are moderator actions that trigger external operations with real-world consequences on Telegram users and chats

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

telegram_manage_chat Rate-limited

telegram_manage_chat stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram_manage_chat": {
      "limits": [
        {
          "counter": "telegram_manage_chat_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about telegram_manage_chat

What does the telegram_manage_chat tool do? +

Manage a Telegram chat (get info, ban, kick, etc.). It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does telegram_manage_chat accept? +

telegram_manage_chat accepts 4 parameters: action, chat_id, user_id, bot_token. Required: action, chat_id, bot_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on telegram_manage_chat? +

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.

What risk level is telegram_manage_chat? +

telegram_manage_chat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit telegram_manage_chat? +

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.

How do I block telegram_manage_chat completely? +

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.

What MCP server provides telegram_manage_chat? +

telegram_manage_chat 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.