Mute or unmute notifications for a Telegram chat. Set muted=true to mute (optionally with duration in seconds), muted=false to unmute
AI agents use telegram-mute-chat to create or update resources in MCP-Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Telegram environment.
This tool creates or modifies data reversibly—it changes the mute status of chat notifications, which can be toggled back at any time. It does not execute arbitrary code, delete data, or involve financial transactions. While it affects user experience and notification behavior, the reversible nature and limited scope (notification settings only) place it in the Write category rather than Execute.
From the tool's definition The tool modifies notification settings for a Telegram chat by setting muted=true/false with optional duration parameters. This is a state change operation that alters chat behavior, qualifying it as a write operation that modifies user preferences reversibly.
Documented attack patterns abuse exactly the kind of access telegram-mute-chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-mute-chat:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-mute-chat": {
"limits": [
{
"counter": "telegram-mute-chat_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}telegram-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.
Mute or unmute notifications for a Telegram chat. Set muted=true to mute (optionally with duration in seconds), muted=false to unmute. It is categorised as a Write tool in the MCP-Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-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 MCP-Telegram. Nothing to install.
telegram-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 telegram-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 telegram-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.
telegram-mute-chat is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, 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.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.