AI agents use set_chat_permissions 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 group/channel permissions for all members, which is a reversible but significant change affecting group governance and user capabilities. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial), but it does create/modify important access controls.
From the tool's definition set_chat_permissions sets group default permissions, which modifies group configuration and member capabilities. The description '设置群组默认权限' (Set group default permissions) indicates structural changes to chat settings.
Documented attack patterns abuse exactly the kind of access set_chat_permissions 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_chat_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"set_chat_permissions": {
"limits": [
{
"counter": "set_chat_permissions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_chat_permissions 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_chat_permissions: 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_chat_permissions 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_chat_permissions 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_chat_permissions. 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_chat_permissions 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.