messaging.telegram.send_message

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/messaging.telegram.send-message.md

WHAT IT DOES

What messaging.telegram.send_message does on Apibase

AI agents use messaging.telegram.send_message to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.

Parameter	Type	Required	Description
`text`	string	Yes	Message text (max 4096 chars). Supports Markdown: bold, _italic_, `code`, [link](url)
`chat_id`	string \| number	Yes	Telegram chat ID (number) or @channel_username (string). Get from get_updates or manually
`parse_mode`	string	—	Text formatting: "Markdown" or "HTML" (default plain text)
`disable_notification`	boolean	—	Send silently without notification sound (default false)

Parameters from the server's own tool schema.

RISK

Why messaging.telegram.send_message is rated Medium

Sends messages to external parties; misuse could cause spam, harassment, or data leaks.

From the tool's definition Send a text message to a Telegram user or group chat

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs messaging.telegram.send_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For messaging.telegram.send_message, this is the rule to start with:

messaging.telegram.send_message Rate-limited

messaging.telegram.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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "messaging.telegram.send_message": {
      "limits": [
        {
          "counter": "messaging.telegram.send_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every messaging.telegram.send_message call is checked against it from then on.

FAQ

Questions about messaging.telegram.send_message

What does the messaging.telegram.send_message tool do? +

⚡ ACTION: Send a text message to a Telegram user or group chat. Supports Markdown (*bold*, _italic_, code, [link](url)) and HTML formatting. Max 4096 chars. Perfect for alerts, notifications, reports (Telegram Bot API). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does messaging.telegram.send_message accept? +

messaging.telegram.send_message accepts 4 parameters: text, chat_id, parse_mode, disable_notification. Required: text, chat_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on messaging.telegram.send_message? +

Register the Apibase MCP server in PolicyLayer and add a rule for messaging.telegram.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 Apibase. Nothing to install.

What risk level is messaging.telegram.send_message? +

messaging.telegram.send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit messaging.telegram.send_message? +

Yes. Add a rate_limit block to the messaging.telegram.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.

How do I block messaging.telegram.send_message completely? +

Set action: deny in the PolicyLayer policy for messaging.telegram.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.

What MCP server provides messaging.telegram.send_message? +

messaging.telegram.send_message is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →