Medium Risk

set_self_destruct_timer

设置消息自毁时间(仅用于秘密聊天或某些特殊场景)

How to control set_self_destruct_timer ↓

What set_self_destruct_timer does on Telegram MCP Complete

AI agents use set_self_destruct_timer to create or update resources in Telegram MCP Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Complete environment.

Medium Risk

Why set_self_destruct_timer needs a policy

This tool modifies message metadata/properties (adding or changing self-destruct timers) rather than destructively deleting messages outright. The effect is reversible by changing or clearing the timer before it activates. It qualifies as Write rather than Destructive because the primary action is configuration/modification, not irreversible deletion.

From the tool's definition Tool description indicates it sets a self-destruct timer on messages (中文: '设置消息自毁时间' = 'set message self-destruct time'). This modifies message properties and behavior in Telegram secret chats.

Documented attack patterns abuse exactly the kind of access set_self_destruct_timer gives an agent:

How to control set_self_destruct_timer

PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for set_self_destruct_timer:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_self_destruct_timer": {
      "limits": [
        {
          "counter": "set_self_destruct_timer_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_self_destruct_timer stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Telegram MCP Complete — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_self_destruct_timer

What does the set_self_destruct_timer tool do? +

设置消息自毁时间(仅用于秘密聊天或某些特殊场景). It is categorised as a Write tool in the Telegram MCP Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_self_destruct_timer? +

Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for set_self_destruct_timer: 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 MCP Complete. Nothing to install.

What risk level is set_self_destruct_timer? +

set_self_destruct_timer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_self_destruct_timer? +

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

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

set_self_destruct_timer is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Telegram MCP Complete tool call.

Start from Telegram MCP Complete, 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.

153 Telegram MCP Complete 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.