forward_message
AI agents use forward_message to create or update resources in Telegram MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Server environment.
Forwarding a message creates a new message in a chat by copying/referencing an existing one. This is a reversible write operation (the forwarded message can be deleted), similar to send_message. The description is empty, so confidence is reduced, but the name and server context strongly imply a message forwarding action with medium blast radius — an AI could forward sensitive messages to unintended recipients.
From the tool's definition Tool name 'forward_message' and server description mentions 'forward messages' as a capability of the Telegram Bot API integration.
Attacks that exploit this kind of access
forward_message. It is categorised as a Write tool in the Telegram MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Server 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 Server. 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 Server MCP server (nexusx-mcp/telegram-mcp-server). 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 →