Critical Risk →

telegram-terminate-session

Terminate a specific Telegram session by its hash, or explicitly terminate all other sessions by setting terminateAllOther=true

How to control telegram-terminate-session ↓

What telegram-terminate-session does on MCP-Telegram

AI agents call telegram-terminate-session 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.

Critical Risk

Why telegram-terminate-session needs a policy

Terminating sessions is an irreversible action that forcibly logs out active Telegram sessions. The ability to terminate 'all other sessions' is particularly severe, as it could lock out legitimate users from all their devices simultaneously with no undo capability.

From the tool's definition 'Terminate a specific Telegram session by its hash, or explicitly terminate all other sessions by setting terminateAllOther=true'

Documented attack patterns abuse exactly the kind of access telegram-terminate-session gives an agent:

How to control telegram-terminate-session

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-terminate-session:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "telegram-terminate-session"
  ]
}

telegram-terminate-session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP-Telegram — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about telegram-terminate-session

What does the telegram-terminate-session tool do? +

Terminate a specific Telegram session by its hash, or explicitly terminate all other sessions by setting terminateAllOther=true. 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.

How do I enforce a policy on telegram-terminate-session? +

Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-terminate-session: 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.

What risk level is telegram-terminate-session? +

telegram-terminate-session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit telegram-terminate-session? +

Yes. Add a rate_limit block to the telegram-terminate-session 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-terminate-session completely? +

Set action: deny in the PolicyLayer policy for telegram-terminate-session. 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-terminate-session? +

telegram-terminate-session 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.

Enforce policy on every MCP-Telegram tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.