AI agents use copy_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.
The tool writes/copies message data to a new location. While it doesn't permanently delete anything, it creates content in a different chat without attribution. The severity is medium rather than high because: (1) it's reversible (copied messages can be deleted), (2) the blast radius is limited to message proliferation in chats the account has access to, and (3) it lacks the destructive finality of deletion or the…
From the tool's definition Tool description (translated) states: 'Copy message to another chat (without showing forward source)'. This creates new message data in a destination chat by duplicating an existing message.
Documented attack patterns abuse exactly the kind of access copy_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 copy_message:
{
"version": "1",
"default": "deny",
"tools": {
"copy_message": {
"limits": [
{
"counter": "copy_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}copy_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 copy_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.
copy_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 copy_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 copy_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.
copy_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.