AI agents call check_qr_status 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 retrieves login status information without modifying any data, executing code, deleting data, or involving financial transactions. It is a read-only status check operation with minimal security risk—an agent checking QR code login status cannot cause harm even if misused.
From the tool's definition Tool name 'check_qr_status' and description '检查指定账号的二维码登录状态和剩余时间' (check QR code login status and remaining time for specified account) indicate a query/status check operation with no data modification.
Documented attack patterns abuse exactly the kind of access check_qr_status 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 check_qr_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_qr_status": {}
}
}check_qr_status 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.
检查指定账号的二维码登录状态和剩余时间. 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 check_qr_status: 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.
check_qr_status 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 check_qr_status 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 check_qr_status. 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.
check_qr_status 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.