AI agents use edit_chat_about 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.
The tool modifies group/channel metadata (the 'about' or description field) but does not delete data or execute arbitrary code. This is a Write operation because it creates or modifies data reversibly. Severity is medium because unauthorized modification of a group's description could mislead members, but the impact is limited to metadata and reversible.
From the tool's definition Tool name 'edit_chat_about' and description '编辑群组/频道简介' (edit group/channel description/about section) indicate modification of chat metadata. This is a reversible write operation that changes group or channel information.
Documented attack patterns abuse exactly the kind of access edit_chat_about 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 edit_chat_about:
{
"version": "1",
"default": "deny",
"tools": {
"edit_chat_about": {
"limits": [
{
"counter": "edit_chat_about_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_chat_about 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 edit_chat_about: 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.
edit_chat_about 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 edit_chat_about 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 edit_chat_about. 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.
edit_chat_about 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.