Kick a user from a Telegram group (removes without permanent ban)
AI agents call telegram-kick-user to permanently remove resources in MCP-Telegram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Kicking a user forcibly removes them from a group. While not a permanent ban, the removal is an immediate, impactful action that expels a person from a community. It is effectively irreversible in the moment (the user is removed and must be re-invited), making it Destructive. Misuse by an AI agent could cause significant social harm by removing users from groups without authorization.
From the tool's definition Kick a user from a Telegram group (removes without permanent ban)
Documented attack patterns abuse exactly the kind of access telegram-kick-user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-kick-user:
{
"version": "1",
"default": "deny",
"hide": [
"telegram-kick-user"
]
} telegram-kick-user 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 Telegram group (removes without permanent ban). It is categorised as a Destructive tool in the MCP-Telegram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-kick-user: 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 MCP-Telegram. Nothing to install.
telegram-kick-user 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-kick-user 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-kick-user. 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-kick-user is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, 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.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.