AI agents call test_proxy 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 tests/checks proxy connectivity and measures response times. It only reads/queries the status of proxies without modifying any data or causing side effects. Equivalent to a ping or health-check operation.
From the tool's definition 测试指定或所有代理的连接状态和响应时间 (Test connection status and response time of specified or all proxies)
Documented attack patterns abuse exactly the kind of access test_proxy 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 test_proxy:
{
"version": "1",
"default": "deny",
"tools": {
"test_proxy": {}
}
} test_proxy 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 test_proxy: 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.
test_proxy 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 test_proxy 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 test_proxy. 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.
test_proxy 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.