Send message using a chat id. Automatically splits long messages that exceed Telegram
AI agents use send-message to create or update resources in Telegram Bot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram Bot MCP Server environment.
This tool creates new messages in Telegram chats, which is a reversible write operation. While not destructive (messages can be deleted), it modifies chat state and could be misused to spam users, send phishing content, or impersonate the bot owner. The high severity reflects the potential blast radius of an AI agent sending unsolicited or malicious messages to many users.
From the tool's definition Tool name 'send-message' and description 'Send message using a chat id' indicate the tool creates and transmits new messages to Telegram chats. The capability to send messages to arbitrary chat IDs constitutes data creation and modification of chat state.
Documented attack patterns abuse exactly the kind of access send-message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram Bot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send-message:
{
"version": "1",
"default": "deny",
"tools": {
"send-message": {
"limits": [
{
"counter": "send-message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send-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.
Send message using a chat id. Automatically splits long messages that exceed Telegram. It is categorised as a Write tool in the Telegram Bot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram Bot 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 Bot 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 Bot MCP Server MCP server (siavashdelkhosh81/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram Bot MCP Server, 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.
16 Telegram Bot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.