AI agents use forward_messages to create or update resources in Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram environment.
Forwarding messages is a reversible write operation that creates new data (forwarded message records) in destination chats without deleting or permanently destroying information. It modifies chat state but can be undone by deleting the forwarded messages. This is less severe than Destructive (which irreversibly removes data) but more severe than Read operations.
From the tool's definition Tool name 'forward_messages' combined with server description stating the server 'Enables AI agents to read, send, and organize Telegram messages and chats.' The sibling tools include 'send_messages' (Write operations) and 'delete_messages' (Destructive…
Attacks that exploit this kind of access
forward_messages. It is categorised as a Write tool in the Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP server in PolicyLayer and add a rule for forward_messages: 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. Nothing to install.
forward_messages is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the forward_messages 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 forward_messages. 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.
forward_messages is provided by the Telegram MCP server (vovavindar/telegram-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 →