AI agents use assign_proxy_to_account 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 account configuration by assigning a proxy setting. It is reversible (the proxy assignment can be changed or removed), making it a Write operation rather than destructive. Severity is medium because proxy manipulation could enable account obfuscation, evasion of restrictions, or facilitate misuse of multiple accounts, but it doesn't directly access sensitive data or cause irreversible damage.
From the tool's definition Tool name 'assign_proxy_to_account' and description '为指定账号分配独立的代理' (assign independent proxy to specified account) indicates modification of account settings. This is a configuration change that creates/modifies the proxy association for an account.
Documented attack patterns abuse exactly the kind of access assign_proxy_to_account 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 assign_proxy_to_account:
{
"version": "1",
"default": "deny",
"tools": {
"assign_proxy_to_account": {
"limits": [
{
"counter": "assign_proxy_to_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}assign_proxy_to_account 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 assign_proxy_to_account: 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.
assign_proxy_to_account 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 assign_proxy_to_account 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 assign_proxy_to_account. 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.
assign_proxy_to_account 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.