AI agents use ban_user 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.
Banning a user from a group modifies group state and user permissions, but this action is reversible—the user can be unbanned later. This distinguishes it from Destructive (irreversible deletion). It does not execute arbitrary code or commands (Execute) and does not involve financial transactions. It is a Write operation that modifies data/state within the Telegram group.
From the tool's definition Tool name 'ban_user' with description '在群组中封禁用户' (ban user in group). This modifies group membership/permissions by restricting a user's access, which is reversible (users can be unbanned).
Documented attack patterns abuse exactly the kind of access ban_user 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 ban_user:
{
"version": "1",
"default": "deny",
"tools": {
"ban_user": {
"limits": [
{
"counter": "ban_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ban_user 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 ban_user: 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.
ban_user 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 ban_user 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 ban_user. 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.
ban_user 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.