AI agents call batch_delete_accounts to permanently remove resources in Telegram MCP Complete — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (entire Telegram accounts) in bulk. Deletion of accounts cannot be undone and represents the most severe category. Even if an AI agent misuses this with incorrect account identifiers, the blast radius is critical—loss of multiple accounts, all associated messages, contacts, and authentication credentials.
From the tool's definition Tool name is 'batch_delete_accounts' and description translates to 'Batch delete multiple accounts'. The action permanently removes multiple Telegram accounts without reversibility.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_delete_accounts gives an agent:
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 batch_delete_accounts:
{
"version": "1",
"default": "deny",
"hide": [
"batch_delete_accounts"
]
}batch_delete_accounts 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.
批量删除多个账号. It is categorised as a Destructive tool in the Telegram MCP Complete MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for batch_delete_accounts: 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.
batch_delete_accounts 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 batch_delete_accounts 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 batch_delete_accounts. 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.
batch_delete_accounts 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.
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.