AI agents use set_global_proxy to create or update resources in Telegram MCP Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Complete environment.
This tool modifies proxy settings across multiple Telegram accounts. While not destructive or financial, it is a write operation that changes system configuration with potentially wide blast radius—improper proxy configuration could redirect all account traffic, compromise communications, or enable interception. The high severity reflects the systemic impact on all accounts managed by this server.
From the tool's definition Tool name 'set_global_proxy' and description '设置全局代理，所有账号默认使用此代理' (set global proxy, all accounts use this proxy by default) indicate a configuration modification that affects all managed accounts systemwide.
Documented attack patterns abuse exactly the kind of access set_global_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 set_global_proxy:
{
"version": "1",
"default": "deny",
"tools": {
"set_global_proxy": {
"limits": [
{
"counter": "set_global_proxy_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_global_proxy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
设置全局代理，所有账号默认使用此代理. It is categorised as a Write tool in the Telegram MCP Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for set_global_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.
set_global_proxy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_global_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 set_global_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.
set_global_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.