AI agents call export_chat to retrieve information from Telegram MCP Complete without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and exports chat history data into JSON format. It retrieves existing data without modifying or deleting anything, making it a Read operation. Severity is medium because chat history may contain sensitive/private communications and the export could expose confidential data if misused.
From the tool's definition 导出聊天记录为JSON格式 (Export chat history as JSON format)
Documented attack patterns abuse exactly the kind of access export_chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for export_chat:
{
"version": "1",
"default": "deny",
"tools": {
"export_chat": {}
}
} export_chat is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
导出聊天记录为JSON格式. It is categorised as a Read tool in the Telegram MCP Complete MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for export_chat: 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 Complete. Nothing to install.
export_chat 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 export_chat 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 export_chat. 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.
export_chat is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Complete, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.