telegram_send_document
Send a document via Telegram bot
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).
Attacks that exploit this kind of access
The rule that runs telegram_send_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For telegram_send_document, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every telegram_send_document call is checked against it from then on.
Questions about telegram_send_document
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.
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.
telegram_send_document 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 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.
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.
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.
This server
Across the catalogue