send_message
AI agents use send_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.
send_message creates new messages and sends them to Telegram chats/users, modifying the state of those conversations reversibly. This is a Write operation with medium severity because misuse could spam users, send malicious content, or harass recipients, but the action is not destructive, financial, or code-executing.
From the tool's definition Server description states the tool enables 'send messages' via Telegram Bot API. The tool name 'send_message' and its placement among other Telegram communication tools (forward_message, get_updates) confirm it creates and transmits data.
Attacks that exploit this kind of access
send_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 send_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.
send_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 send_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 send_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.
send_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 →