telegram_send_audio
AI agents use telegram_send_audio to create or update resources in Agent Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Telegram environment.
This tool sends audio files to Telegram, which is a write operation that creates new data (audio messages) in chats. It is reversible via telegram_delete_message, so it does not qualify as Destructive. The blast radius is medium: an agent could spam audio to chats or send inappropriate content, but the impact is limited to message creation without financial or code-execution consequences.
From the tool's definition Tool name is 'telegram_send_audio' on a Telegram MCP server that 'enables AI agents to send and receive messages, media, and files on Telegram'. The 'send_audio' action creates and transmits media content to Telegram chats.
Attacks that exploit this kind of access
telegram_send_audio. It is categorised as a Write tool in the Agent Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Telegram MCP server in PolicyLayer and add a rule for telegram_send_audio: 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 Agent Telegram. Nothing to install.
telegram_send_audio 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_audio 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_audio. 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_audio is provided by the Agent Telegram MCP server (tharindumendis/agent_telegeam_mcp). 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 →