텔레그램 채팅에 장소(위치+이름+주소)를 전송합니다.
AI agents use telegram_send_venue to create or update resources in Telegram MCP Server & Channel Monitor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Server & Channel Monitor environment.
The tool creates/adds data (a venue message) in a Telegram chat without destructive effects. It falls under Write category because it modifies chat state by adding a new message. Severity is medium because misuse could spam channels or send incorrect location information, but the impact is limited to chat content creation and is reversible.
From the tool's definition Tool sends venue data (location, name, address) to Telegram chat. This creates new message content in the chat, which is reversible (can be deleted via telegram_delete_message).
Attacks that exploit this kind of access
텔레그램 채팅에 장소(위치+이름+주소)를 전송합니다. It is categorised as a Write tool in the Telegram MCP Server & Channel Monitor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Server & Channel Monitor MCP server in PolicyLayer and add a rule for telegram_send_venue: 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 Server & Channel Monitor. Nothing to install.
telegram_send_venue 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_venue 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_venue. 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_venue is provided by the Telegram MCP Server & Channel Monitor MCP server (ruchiayeon/telegram-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 →