New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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)

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-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.

ParameterTypeRequiredDescription
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

Questions about messaging.telegram.send_photo

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

⚡ 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.

What parameters does messaging.telegram.send_photo accept? +

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.

How do I enforce a policy on messaging.telegram.send_photo? +

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.

What risk level is messaging.telegram.send_photo? +

messaging.telegram.send_photo 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_photo? +

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.

How do I block messaging.telegram.send_photo completely? +

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.

What MCP server provides messaging.telegram.send_photo? +

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.

Across the catalogue

// 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 Apibase'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.