Get information about a chat (group, channel, or user).
AI agents call telegram_get_chat_info to retrieve information from Agent Telegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Telegram chats without any side effects. It performs a query operation ('Get information') that does not create, modify, delete, or execute any actions. The severity is low because chat metadata exposure has limited direct impact compared to message manipulation or financial operations. Confidence is high as the intent and behavior are clearly defined.
From the tool's definition Tool name 'telegram_get_chat_info' and description 'Get information about a chat (group, channel, or user)' indicate a read-only retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get information about a chat (group, channel, or user). It is categorised as a Read tool in the Agent Telegram MCP Server, which means it retrieves data without modifying state.
Register the Agent Telegram MCP server in PolicyLayer and add a rule for telegram_get_chat_info: 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_get_chat_info 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_chat_info 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_chat_info. 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_chat_info 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 →