Send text or markdown message via telegram bot
AI agents use tg_send_message to create or update resources in Notify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notify MCP Server environment.
The tool sends messages via Telegram, which is a Write action (creates data/content). It is not destructive (messages can be deleted), not financial, not execute (does not run arbitrary code), and not a Read operation. Severity is medium because misuse could enable spam, social engineering, or unauthorized communication, but the action is reversible and does not directly impact critical systems or finances.
From the tool's definition Tool description states 'Send text or markdown message via telegram bot' — this creates/posts a message to Telegram, a reversible write operation.
Documented attack patterns abuse exactly the kind of access tg_send_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notify MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tg_send_message:
{
"version": "1",
"default": "deny",
"tools": {
"tg_send_message": {
"limits": [
{
"counter": "tg_send_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tg_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 text or markdown message via telegram bot. It is categorised as a Write tool in the Notify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notify MCP Server MCP server in PolicyLayer and add a rule for tg_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 Notify MCP Server. Nothing to install.
tg_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 tg_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 tg_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.
tg_send_message is provided by the Notify MCP Server MCP server (oci:ghcr.io/aahl/mcp-notify:latest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notify 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.
21 Notify MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.