현재 봇의 기본 정보(이름, username, id 등)를 조회합니다.
AI agents call telegram_get_me to retrieve information from Telegram MCP Server & Channel Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves bot metadata without modifying, executing operations, or affecting external systems. It is a simple read operation that returns static bot information, posing minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states it '조회합니다' (retrieves/queries) the current bot's basic information (name, username, id, etc.). The verb '조회' explicitly indicates data retrieval with no side effects.
Attacks that exploit this kind of access
현재 봇의 기본 정보(이름, username, id 등)를 조회합니다. It is categorised as a Read tool in the Telegram MCP Server & Channel Monitor MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Server & Channel Monitor MCP server in PolicyLayer and add a rule for telegram_get_me: 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_get_me is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the telegram_get_me 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_get_me. 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_get_me 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 →