messaging.telegram.send_photo
⚡ ACTION: Send a photo to a Telegram chat with optional caption. Provide image URL — supports JPG, PNG, GIF up to 10MB (Telegram Bot API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/messaging.telegram.send-photo.md
What messaging.telegram.send_photo does on Apibase
AI agents use messaging.telegram.send_photo 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 |
|---|---|---|---|
photo | string | Yes | Photo URL (https://...) or Telegram file_id from previous upload |
caption | string | — | Photo caption (max 1024 chars) |
chat_id | string | number | Yes | Target chat ID or @channel_username |
Parameters from the server's own tool schema.
Why messaging.telegram.send_photo is rated Medium
Sends media content to external chat; irreversible external communication with high misuse potential.
From the tool's definition Send a photo to a Telegram chat with optional caption
Attacks that exploit this kind of access
The rule that runs messaging.telegram.send_photo 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_photo, this is the rule to start with:
messaging.telegram.send_photo 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 Apibase, apply this rule, and every messaging.telegram.send_photo call is checked against it from then on.
Questions about messaging.telegram.send_photo
⚡ ACTION: Send a photo to a Telegram chat with optional caption. Provide image URL — supports JPG, PNG, GIF up to 10MB (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.
messaging.telegram.send_photo accepts 3 parameters: photo, caption, chat_id. Required: photo, chat_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for messaging.telegram.send_photo: 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.
messaging.telegram.send_photo 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 messaging.telegram.send_photo 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 messaging.telegram.send_photo. 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.
messaging.telegram.send_photo 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue