AI agents use forward_message 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.
Forwarding messages is a write operation that replicates message content to another chat destination. It does not execute code, delete data irreversibly, or move money. While it could facilitate spam or harassment if misused by an AI agent across multiple accounts (especially given the 'multi-account' capability context), the action itself is reversible and creates data rather than destroying it.
From the tool's definition Tool name 'forward_message' with description '转发消息到另一个聊天' (forward message to another chat). This creates a copy of a message in a different location, which is a reversible modification action.
Documented attack patterns abuse exactly the kind of access forward_message 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 forward_message:
{
"version": "1",
"default": "deny",
"tools": {
"forward_message": {
"limits": [
{
"counter": "forward_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}forward_message 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.
Free to start. No card required.
转发消息到另一个聊天. 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.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for forward_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 Telegram MCP Complete. Nothing to install.
forward_message 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_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 forward_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.
forward_message 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.