AI agents call telegram-leave-group 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.
Leaving a group or channel is an irreversible action in the sense that it removes the user's membership, potentially losing access to message history and requiring a new invite to rejoin. The action cannot be automatically undone and has significant social/operational consequences.
From the tool's definition Leave a Telegram group or channel
Documented attack patterns abuse exactly the kind of access telegram-leave-group 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-leave-group:
{
"version": "1",
"default": "deny",
"hide": [
"telegram-leave-group"
]
} telegram-leave-group 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.
Leave a Telegram group or channel. 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-leave-group: 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-leave-group 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-leave-group 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-leave-group. 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-leave-group 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.