message_action
Edit, delete, forward, copy, react to, pin, unpin or otherwise manage Telegram messages through an official Bot API method.
This record as markdown: /tools/cyuanxv-telegram-bot-mcp-server/message-action.md
What message_action does on Telegram Bot
AI agents call message_action to permanently remove resources in Telegram Bot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why message_action is rated Critical
An AI agent that decides to call message_action doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Telegram Bot is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs message_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Telegram Bot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For message_action, this is the rule to start with:
message_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Telegram Bot, apply this rule, and every message_action call is checked against it from then on.
Questions about message_action
Edit, delete, forward, copy, react to, pin, unpin or otherwise manage Telegram messages through an official Bot API method. It is categorised as a Destructive tool in the Telegram Bot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Telegram Bot MCP server in PolicyLayer and add a rule for message_action: 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 Bot. Nothing to install.
message_action 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 message_action 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 message_action. 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.
message_action is provided by the Telegram Bot MCP server (@cyuanxv/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Telegram Bot, and thousands of servers like it.
Across the catalogue