Delete a message from a chat (bot must have delete permission).
AI agents call telegram_delete_message to permanently remove resources in Agent Telegram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes messages, which cannot be undone. Deletion is the hallmark of the Destructive category. While the blast radius is limited to chat message history rather than financial systems or system-level operations, the irreversible nature and potential for abuse (e.g., deleting evidence, disrupting communication) justifies 'high' severity. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'telegram_delete_message' and description 'Delete a message from a chat' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete a message from a chat (bot must have delete permission). It is categorised as a Destructive tool in the Agent Telegram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agent Telegram MCP server in PolicyLayer and add a rule for telegram_delete_message: 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 Agent Telegram. Nothing to install.
telegram_delete_message 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_delete_message 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_delete_message. 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_delete_message is provided by the Agent Telegram MCP server (tharindumendis/agent_telegeam_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →