telegram_copy_message
AI agents use telegram_copy_message to create or update resources in Telegram MCP Server & Channel Monitor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Server & Channel Monitor environment.
Copying a message is a write operation—it creates new data (a duplicate message) in the destination chat. While reversible (the copy can be deleted), it modifies the state of the chat by introducing new content.
From the tool's definition Tool name 'telegram_copy_message' indicates it creates a copy of a message. The sibling tools include 'telegram_copy_messages' (plural) and other message manipulation functions like 'telegram_edit_message', 'telegram_forward_message', which are write…
Attacks that exploit this kind of access
telegram_copy_message. It is categorised as a Write tool in the Telegram MCP Server & Channel Monitor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Server & Channel Monitor MCP server in PolicyLayer and add a rule for telegram_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 Server & Channel Monitor. Nothing to install.
telegram_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 telegram_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 telegram_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.
telegram_copy_message is provided by the Telegram MCP Server & Channel Monitor MCP server (ruchiayeon/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 →