telegram_send_document

Send a document via Telegram bot

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/telegram-send-document.md

What telegram_send_document does on ScopeGate

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

Why telegram_send_document is rated Medium

The tool creates/sends a message artifact (document) through Telegram, which is a reversible write action. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve data (not Read).

From the tool's definition Tool name 'telegram_send_document' and description 'Send a document via Telegram bot' indicate creation/transmission of data (a document delivery action). This is a write/send operation that modifies state in an external system (Telegram chat/channel).

Questions about telegram_send_document

What does the telegram_send_document tool do? +

Send a document via Telegram bot. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telegram_send_document? +

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

What risk level is telegram_send_document? +

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 telegram_send_document? +

Yes. Add a rate_limit block to the 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 telegram_send_document completely? +

Set action: deny in the PolicyLayer policy for 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 telegram_send_document? +

telegram_send_document is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScopeGate, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ScopeGate's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.