telegram_send_media
Send media (photo/document/video) via Telegram.
This record as markdown: /tools/creativelead-unclick/telegram-send-media.md
What telegram_send_media does on UnClick
AI agents use telegram_send_media to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
caption | string | — | |
chat_id | string | — | |
bot_token | string | — | |
media_url | string | — | |
media_type | string | — | photo, document, video, audio |
Parameters from the server's own tool schema.
Why telegram_send_media is rated Medium
This tool sends media messages, which is a write operation that modifies state (adds messages to a Telegram conversation). It creates new data on an external service. While reversible (messages can be deleted), sending unsolicited messages to Telegram users, impersonation, spam, or harassment via this tool represents a medium-severity risk.
From the tool's definition Tool name 'telegram_send_media' and description 'Send media (photo/document/video) via Telegram' indicate the tool creates/sends content through Telegram.
Attacks that exploit this kind of access
The rule that runs telegram_send_media safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For telegram_send_media, this is the rule to start with:
telegram_send_media 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 UnClick, apply this rule, and every telegram_send_media call is checked against it from then on.
Questions about telegram_send_media
Send media (photo/document/video) via Telegram. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
telegram_send_media accepts 5 parameters: caption, chat_id, bot_token, media_url, media_type. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for telegram_send_media: 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 UnClick. Nothing to install.
telegram_send_media 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_media 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_media. 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_media is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue