messaging.telegram.send_document

⚡ ACTION: Send a file/document to a Telegram chat — PDF, CSV, ZIP, any format up to 50MB. Perfect for sending reports, data exports, generated files (Telegram Bot API)

SERVERApibase SOURCEapibase-mcp-client

Medium RISK CLASS

Category Write

Parameters 32 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-document.md

WHAT IT DOES

What messaging.telegram.send_document does on Apibase

AI agents use messaging.telegram.send_document 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
`caption`	string	—	Document caption
`chat_id`	string \| number	Yes	Target chat ID or @channel_username
`document`	string	Yes	Document URL (https://...) — PDF, CSV, ZIP, etc.

Parameters from the server's own tool schema.

RISK

Why messaging.telegram.send_document is rated Medium

Creates and sends data to external messaging service; reversible but affects third-party communication channels.

From the tool's definition Send a file/document to a Telegram chat — PDF, CSV, ZIP

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs messaging.telegram.send_document 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_document, this is the rule to start with:

messaging.telegram.send_document Rate-limited

messaging.telegram.send_document 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_document": {
      "limits": [
        {
          "counter": "messaging.telegram.send_document_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_document call is checked against it from then on.

FAQ

Questions about messaging.telegram.send_document

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

⚡ ACTION: Send a file/document to a Telegram chat — PDF, CSV, ZIP, any format up to 50MB. Perfect for sending reports, data exports, generated files (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_document accept? +

messaging.telegram.send_document accepts 3 parameters: caption, chat_id, document. Required: chat_id, document. 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_document? +

Register the Apibase MCP server in PolicyLayer and add a rule for messaging.telegram.send_document: 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_document? +

messaging.telegram.send_document 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_document? +

Yes. Add a rate_limit block to the messaging.telegram.send_document 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_document completely? +

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

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