AI agents use demote_admin 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 action creates a reversible modification to user permissions and group/channel administrative structure. It is not destructive (the admin account still exists), not financial, and not executing arbitrary code. However, it has potential for misuse in Telegram group management contexts, as unauthorized role changes could disrupt group governance.
From the tool's definition Tool name 'demote_admin' and description translate to 'demote administrator to ordinary member' - this modifies user roles/permissions within a Telegram group or channel by changing an admin's status to a regular member.
Documented attack patterns abuse exactly the kind of access demote_admin 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 demote_admin:
{
"version": "1",
"default": "deny",
"tools": {
"demote_admin": {
"limits": [
{
"counter": "demote_admin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}demote_admin 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 demote_admin: 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.
demote_admin 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 demote_admin 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 demote_admin. 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.
demote_admin 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.