AI agents use mute_chat 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.
Muting chat notifications is a write operation that modifies user preferences/settings without destructive consequences. The change is fully reversible (notifications can be unmuted). It affects only notification behavior, not data deletion or financial transactions. Severity is low because the blast radius of unintended muting is minimal—users simply won't receive notifications until the setting is changed back.
From the tool's definition Tool name 'mute_chat' with description '静音聊天通知' (mute chat notifications). The tool modifies chat notification settings, a reversible preference change.
Documented attack patterns abuse exactly the kind of access mute_chat 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 mute_chat:
{
"version": "1",
"default": "deny",
"tools": {
"mute_chat": {
"limits": [
{
"counter": "mute_chat_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mute_chat 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 mute_chat: 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.
mute_chat 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 mute_chat 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 mute_chat. 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.
mute_chat 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.