Kick a user from a group, a supergroup or a channel. Provides detailed error information if the operation fails.
AI agents call kick-chat-member to permanently remove resources in Telegram Bot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Kicking a user is a destructive, hard-to-reverse action: the user is expelled from the chat and their membership is terminated. While a re-invite is theoretically possible, the action itself cannot be automatically undone and has significant social/operational impact. This qualifies as Destructive rather than Write because it removes access/membership rather than modifying data.
From the tool's definition 'Kick a user from a group, a supergroup or a channel' — forcibly removes a user from a chat, which is an irreversible removal action (the user loses access and must be re-invited).
Documented attack patterns abuse exactly the kind of access kick-chat-member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram Bot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kick-chat-member:
{
"version": "1",
"default": "deny",
"hide": [
"kick-chat-member"
]
} kick-chat-member disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Kick a user from a group, a supergroup or a channel. Provides detailed error information if the operation fails. It is categorised as a Destructive tool in the Telegram Bot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Telegram Bot MCP Server MCP server in PolicyLayer and add a rule for kick-chat-member: 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 Telegram Bot MCP Server. Nothing to install.
kick-chat-member 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 kick-chat-member 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 kick-chat-member. 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.
kick-chat-member is provided by the Telegram Bot MCP Server MCP server (siavashdelkhosh81/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram Bot MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Telegram Bot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.