send_photo_file
AI agents use send_photo_file to create or update resources in Telegram Mcp Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram Mcp Kit environment.
Sending a photo file to a Telegram chat creates new data/content that persists and is visible to recipients. This is reversible (the message can be deleted by edit_message or delete_message tools also present), making it Write rather than Destructive. Severity is high because an AI agent could spam, harass, or send inappropriate images to unintended recipients or chats, causing reputational and operational damage.
From the tool's definition Tool name 'send_photo_file' indicates sending/uploading a photo file to Telegram. Server description states 'message sending' and 'file handling' as core capabilities.
Attacks that exploit this kind of access
send_photo_file. It is categorised as a Write tool in the Telegram Mcp Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram Mcp Kit MCP server in PolicyLayer and add a rule for send_photo_file: 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 Telegram Mcp Kit. Nothing to install.
send_photo_file 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 send_photo_file 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 send_photo_file. 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.
send_photo_file is provided by the Telegram Mcp Kit MCP server (quoctang/telegram-mcp-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →