telegram_get_file_info
AI agents call telegram_get_file_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.
The tool appears to query file metadata from Telegram, a read-only operation with no side effects. While the description is empty, the naming convention and context of sibling tools (particularly telegram_download_file and other information retrieval tools) strongly suggest this retrieves file information without modifying or executing anything.
From the tool's definition Tool name 'telegram_get_file_info' indicates retrieval of file metadata. Sibling tools like 'telegram_download_file' perform Read operations (fetch data without side effects), and 'telegram_get_*' prefixed tools consistently retrieve information.
Attacks that exploit this kind of access
telegram_get_file_info. 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_file_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_file_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_file_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_file_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_file_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 →